POST /v1/responses). Xenovia supports that endpoint natively, so each agent turn is traced and policy-checked without changing your orchestration flow.
Setup
Single agent
Runner.run call may produce multiple Responses API turns. Each turn creates an independent trace in Xenovia. Use a session ID to group them.
Sessions via previous_response_id
The Responses API natively chains turns using previous_response_id. Xenovia’s session plugin recognises this field and automatically resolves sessions across chained calls, so you do not need an explicit session ID header if the SDK manages previous_response_id for you.
To also group runs explicitly:
X-Xenovia-Session-Id takes priority over the previous_response_id chain. Use explicit IDs when you need grouping across separate Runner.run calls.
Multi-agent handoff
session_id in the Traces view to see the full conversation in order.
Agents with tools
input.tool_names in the Rego policy. A block rule matching the tool name returns 403 before the model is called.
Handling policy blocks
X-Xenovia-Trace-Id header on the 403 response identifies the blocking trace in the platform.