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
Run ID returned by POST /v1/agent/answer/runs
Query Parameters
SSE resume cursor (Accept: text/event-stream only). Replay events with seq strictly greater than this value. Equivalent to the Last-Event-ID header.
x >= 0Response
Current state of the agent run. With Accept: text/event-stream, resumes/tails 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 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 the [n] markers join; cards reuse the sibling TakoCard; metadata carries definitions/assumptions/ methodology. NO inline data, NO structured output, NO web_results — ever. Prose-only (empty cards) is legitimate.
Cost-plus usage for one metered request. total_cost_usd is always present
(the total quoted charge). compute / data are the additive breakdown and
appear only where they apply. See module docstring for the quote-vs-drawdown
caveat and the total == compute + data invariant.
Request body for POST /v1/agent/answer/runs.
Frozen contract: NO output_schema / structured outputs, NO inline data — ever. Cards are the only data-export path (via /v1/contents).