Cancel Agent Test Run
Cancel a non-terminal test run. Idempotent on a terminal run
(completed / failed / cancelled) - the call returns the
unchanged run.
Authentication
Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.
Path parameters
Headers
Response
The (possibly already-terminal) test run.
Prefixed wire identifier (run_<26 char Crockford base32>).
URL paths accept only this
prefixed form; legacy UUID path parameters are rejected with
404.
Prefixed wire identifier (test_<26 char Crockford base32>)
of the parent test.
Prefixed wire identifier (agent_<26 char Crockford base32>)
of the agent this run executed against.
The one lifecycle vocabulary shared by every async job (batch
calls, knowledge-base imports, agent-test runs, suite runs):
pending → running → a terminal state.
pending- accepted but not yet executing (queued for a worker, or deferred to a future scheduled time).running- actively executing.completed- ran to conclusion. The single terminal-success verb. For a job that produces a pass/fail judgment (an agent-test run), this means it produced a verdict - read the separateverdictfield for the judgment, not this status.failed- could not complete (an infrastructure or input failure), distinct from acompletedjob whoseverdictisfailed.cancelled- cancelled before reaching a natural terminal state.
The pass/fail judgment, present only once the run reached a
verdict (status is completed).
Human-readable error message when status is failed.