Generate a capability document
Starts generating the agent’s capability document from its published configuration and returns 202 with the run’s workflow_id. Generation runs in the background; poll GET /core/agents/{agent_id}/capability-document until status is ready. Generation only happens when you ask for it: publishing a new agent version doesn’t regenerate the document, but marks it stale.
Answers 422 when the configuration isn’t eligible (see the preflight endpoint), 409 when a generation for the agent is already running, and 404 when the agent has no published version. Requires agents:manage.
Headers
Organization ID for user PATs (pat_ prefix tokens)
Path Parameters
Query Parameters
The agent version to generate from. Defaults to the latest published version.
Generation mode: one_opus (the default) or question, which works capability by capability and suits a sparse configuration.
Your organization's slug, used to link back to the agent in the notification email. Optional.

