API
Responses
Use the OpenAI Responses contract through governed routing
POST /v1/responses accepts the Responses request shape through either compatibility prefix. This is a source contract until the deployed OpenAPI drift gate and an authenticated production synthetic both pass.
Endpoint and scope
Use a workspace credential with route scope. The same tenant, product, policy and provider eligibility checks used by Chat Completions apply before dispatch.
POST https://api.octoryn.dev/v1/responses
Authorization: Bearer $OCTORYN_API_KEY
Content-Type: application/jsonRequest shape
Send model plus input in the Responses shape. Tools, reasoning controls, structured output and other optional fields remain route-specific capabilities.
{
"model": "policy/frontier",
"input": "Summarise the production risks.",
"stream": false
}Native event streaming
Set stream=true for text/event-stream. Responses uses named native events rather than the Chat Completions data: [DONE] topology. Handle cancellation, terminal error events and incomplete output explicitly.
Native or translated provider paths
Router may use a native Responses provider or a compatible translated path. The client contract stays Responses-shaped while policy, health and capability eligibility remain enforced.