capability_documents

Generate Capability Document

Start a generation. Manual trigger only — nothing calls this automatically.

one_opus is the default: it is the engine the reference documents were written by, which is checkable rather than assumed — it titles a document the way a writer would ("GameStop"), and the staged engine cannot, because extract deliberately keeps the platform label out of the persona and the title comes from the persona ("The assistant"). Its coverage headers are written per document for the same reason.

Both engines now face check_structure, so neither can report a clean run on a document with no sample conversation in it. engine=question still selects the staged engine: it asks one question per capability and repairs what the checks reject, which is the better shape when a config is thin enough that a single call has little to go on.

post/core/agents/{agent_id}/capability-document

Request

  • Base URL
    https://api.anyreach.ai (the document declares no server; this is the origin it was published from)
  • Auth
    HTTP bearer

Path parameters

agent_idstring required

Query parameters

config_versioninteger nullable
enginestring
org_slugstring

Headers

x-anyreach-orgstring nullable

Organization ID for user PATs (pat_ prefix tokens)

Response

Successful Response

agent_idstring required
workflow_idstring required
status'pending' | 'running' | 'ready' | 'quality_failed' | 'failed' | 'ineligible' required

Changes

No recorded changes to this operation across all 1 revision of this API.