Skip to main content
An intention is a named pattern — “Customer Support Lookup”, “Pipeline Review” — with an intent class, optional approval requirement, an allowed data-element list, and a token TTL. Every intent evaluation either matches an active intention or falls into the ambient cluster.

Endpoints

Creating or publishing an intention requires the policy_write or admin scope on the API key.

Intention object

intent_class is one of reporting, export, admin, lookup, analysis, write, other. status is draft, active, or archived — only active intentions match traffic.

List intentions

Response:

Create an intention

Returns 201 Created with the new intention object. Status defaults to draft.

Publish

Promotes a draft to active. The next matching tool call is decided against the intention immediately.

Errors

403 if the API key lacks policy_write. 409 if a label collides with an existing intention.