Poll an Answer Agent run
Retrieve the current state and result of an Answer Agent run
Notes
- Poll with the
run_idreturned by Dispatch an Answer Agent run.statusprogressesqueued→running→completed/failed; theresult(anAnswerAgentResult) is populated oncestatusiscompleted. - The result carries
answer(markdown with[n]citation markers),citations(the registry those markers join),cards, andmetadata. There is nostructured_outputand noweb_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. Usestarting_after(or theLast-Event-IDheader) to replay only events whoseseqis greater than a value you’ve already seen. See the Answer Agent guide.
Authorizations
Path Parameters
The run ID from the POST /v1/agent/answer/runs response.
Query Parameters
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.
x >= 0Response
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).
queued, running, completed, failed "agent.run"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.
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 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).