Create an agent run
Start a new agent run from the API key’s agent.
The key alone determines the organization and agent. template_id is
only a cross-check: if it doesn’t match the key’s agent, the API returns
403. The API delivers files to the agent’s workspace before it processes
input_text. The API responds immediately with the run’s ID. Because
execution is asynchronous, poll GET /v1/agents/{agent_id} for progress.
Besides schema validation, the API also returns 422 when a file is not valid base64 or when the organization has no usable inference model.
See the Sending files and Errors and retries guides.
Authorizations
API key (ak_...) as a Bearer token. Preferred.
Body
Display name for the run, shown in the Clicks app.
1 - 200The ID of the agent that the API key belongs to. The key determines which agent runs; this field is only a cross-check, and a mismatch returns 403.
Up to 10 files with a combined decoded size of 10 MiB. The API delivers them to the agent's workspace before it processes input_text, so the input can reference them by filename.
10The agent's first input. Always send it: without it, the API creates the run but never starts a turn — the idle run reports finished until someone provides input in the Clicks app, and may be stopped automatically.
Response
Successful Response
Returned immediately; the run executes asynchronously.
The ID of the created run. Poll GET /v1/agents/{agent_id} for its status and transcript.