Stop a run
Agent
Stop a run
Gracefully stop a running Agent run and keep the results gathered so far.
POST
Stop a run
If the run is still active, the agent wraps up and completes the run early with the results gathered so far. The run ends with status
completed and stopReason: stopped. You are billed for usage accrued before the stop. If the run has already reached a terminal status (completed, failed, or cancelled), the endpoint returns the existing run unchanged.
To terminate a run immediately without returning any results, use cancel instead.
Only supported on
max effort runs. Exa-Beta: agent-max-effort-2026-07-27 must be
passed as a request header. The header accepts a comma-separated list of beta tokens.Get your Exa API key
Authorizations
Pass your Exa API key in the x-api-key header. You can also authenticate with Authorization: Bearer .
Headers
Comma-separated beta feature tokens for opting into experimental features.
Path Parameters
Agent run ID.
Required string length:
1 - 200Pattern:
^[A-Za-z0-9_.:-]+$Example:
"agent_run_01j7x9v0m2n4p6q8r0s2t4v6w8"
Response
Agent run
Agent run ID. New run IDs are returned with the agent_run_ prefix.
Required string length:
1 - 200Pattern:
^[A-Za-z0-9_.:-]+$Example:
"agent_run_01j7x9v0m2n4p6q8r0s2t4v6w8"
Allowed value:
"agent_run"Available options:
queued, running, completed, failed, cancelled Why the run stopped. null while the run is queued or running.
Available options:
schema_satisfied, budget_reached, stopped, error, cancelled When the run was created
Canonicalized request fields stored with the run.