roasOSGet agent run events
The ordered lifecycle of one run: accepted, started, tool_called, gate_opened, gate_auto_approved, generation_started, settled, failed, cancelled. A run older than the timeline falls back to the steps its own timestamps can prove.
The ordered lifecycle of one run: accepted, started, tool_called, gate_opened, gate_auto_approved, generation_started, settled, failed, cancelled. A run older than the timeline falls back to the steps its own timestamps can prove.
Authorization
bearerAuth API key authentication. Use your API key as the bearer token: Authorization: Bearer roasos_sk_...
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/agent-runs/497f6eca-6276-4993-bfeb-53cbbbba6f08/events"{ "data": [ { "seq": 0, "event": "accepted", "at": "2019-08-24T14:15:22Z" } ]}Get an agent run result
What the agent answered, the thread it wrote it in, and what the run cost. A run that is not terminal answers 409 run_not_completed.
Cancel an agent run
Ask a run that has not finished to stop. The unused reservation is refunded. A generation the run already started keeps its own lifecycle — cancel that at POST /v1/jobs/{id}/cancel. A run that already finished answers 409 run_not_cancelable.