Verify report and stream response
Run verification on a report — each claim is checked against its cited sources — streaming verdict events as Server-Sent Events. Use before sharing a report externally.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
Optional extra verification instructions (e.g. which claims to scrutinize).
Existing conversation to run the verification in; a new one starts when omitted.
Optional title for the verification conversation.
Project file ids to include as verification context.
Project file ids referenced in the instructions.
Response
Server-Sent Events stream of agent activity.
Each event is a UTF-8 line prefixed with event:, id:, or data: per the SSE spec. The data: payload is a JSON object with the shape {"type": <event_type>, "sequence": <int>, "data": <object>}.
Event types emitted by the agent:
status— high-level progress;data.message(queued/running text) ordata.summary(short status line)tool.started— agent invoked a tool;data.id,data.nametool.input— tool input arguments;data.id,data.name,data.inputtool.completed— tool finished;data.idmessage.delta— incremental assistant text;data.text(append in order)done— terminal event;data.messageId,data.content(final assistant message),data.status(complete/error/cancelled)
Resumability: when the connection drops before done, the same stream can be resumed via GET /v1/projects/{project_id}/conversations/{chat_id}/messages/{message_id}/events.