Skip to main content
GET
Poll an answer agent run

Notes

  • Poll with the run_id returned by Dispatch an Answer Agent run. status progresses queuedrunningcompleted / failed; the result (an AnswerAgentResult) is populated once status is completed.
  • The result carries answer (markdown with [n] citation markers), citations (the registry those markers join), cards, and metadata. There is no structured_output and no web_results — a prose-only answer with no cards is legitimate.
  • To resume or tail the run as a live Server-Sent Events stream, send Accept: text/event-stream. Use starting_after (or the Last-Event-ID header) to replay only events whose seq is greater than a value you’ve already seen. See the Answer Agent guide.

Authorizations

X-API-Key
string
header
required

Path Parameters

run_id
string
required

The run ID from the POST /v1/agent/answer/runs response.

Query Parameters

starting_after
integer

SSE resume cursor (Accept: text/event-stream only). The stream replays events with seq greater than this value. It is equivalent to the Last-Event-ID header.

Required range: x >= 0

Response

Current state of the agent run. With Accept: text/event-stream, the response replays and then follows the run as an SSE stream of AnswerAgentStreamEnvelope events. Use starting_after or Last-Event-ID to resume. If the stream ends without an agent_result event, poll this endpoint with Accept: application/json for the terminal status.

The answer-agent run resource returned by dispatch (202) and poll (GET).

run_id
string
required
status
enum<string>
required
Available options:
queued,
running,
completed,
failed
created_at
string
required
object
string
default:agent.run
Allowed value: "agent.run"
thread_id
string | null
completed_at
string | null
result
AnswerAgentResult · object | null

Final answer-agent output. answer is markdown prose with [n] citation markers. citations is the unified top-level registry that the [n] markers join. cards reuse the sibling TakoCard. metadata carries definitions, assumptions, and methodology. There is no inline data, no structured output, and no web_results — ever. A prose-only result (empty cards) is legitimate.

error
ErrorObject · object | null
usage
Usage · object | null

Usage for one metered request. total_cost_usd is always present (the total quoted charge). compute and data are the additive breakdown; each appears only where it applies. total_cost_usd always equals the sum of the components that appear.

request
AnswerAgentRunRequest · object | null

Request body for POST /v1/agent/answer/runs.

Frozen contract: no output_schema, no structured outputs, and no inline data — ever. Cards are the only data-export path (via /v1/contents).