Create a model response using the OpenAI Response API format
Auriko routes the request to the optimal provider based on your routing preferences (cost, latency, throughput, etc.).Documentation Index
Fetch the complete documentation index at: https://docs.auriko.ai/llms.txt
Use this file to discover all available pages before exploring further.
gateway.models[] instead of model to route across multiple modelsgateway.routing objectextensionsrouting_metadata with cost breakdownAPI key authentication.
Keys start with ak_ prefix.
Example: Authorization: Bearer ak_live_xxxxxxxxxxxx
Request body for creating a response via the Response API.
Model ID to use (e.g., "gpt-4o", "claude-sonnet-4-20250514").
The input to generate a response for.
System instructions for the model.
Tools available to the model.
A tool available to the model.
How the model should use tools.
auto, none, required Whether the model can make multiple tool calls in parallel.
Maximum number of output tokens.
Sampling temperature.
0 <= x <= 2Nucleus sampling parameter.
0 <= x <= 1Top-k sampling parameter.
Number of top logprobs to return per token position. Requires provider logprobs support.
0 <= x <= 20Whether to stream the response.
Text generation configuration.
Reasoning/thinking configuration.
Truncation strategy for long inputs.
Arbitrary key-value metadata.
Additional data to include in the response.
End-user identifier for abuse detection.
Omit this field or set to false. Sending true returns 400.
false Auriko gateway directives.
Auriko extensions for provider-specific passthrough.
For reasoning control, use the top-level reasoning_effort parameter
instead of extensions.
Pass provider-specific parameters directly:
anthropic: Anthropic-specific parametersopenai: OpenAI-specific parametersgoogle: Google/Gemini-specific parametersdeepseek: DeepSeek-specific parametersPassthrough parameters are forwarded as-is to the target provider.
Key for prompt caching.
Safety policy identifier.
Successful response.
For non-streaming requests, returns a ResponseObject.
For streaming (stream: true), returns Server-Sent Events in
the Response API format: event: <type>\ndata: <json>\n\n.
A completed Response API response.
Unique response identifier.
Unix timestamp of creation.
Model used for generation.
Response status.
completed, failed, incomplete, in_progress Output items generated by the model. Known types include
message, function_call, and reasoning. Additional types
from the provider (e.g., web_search_call, file_search_call)
are passed through verbatim.
An output item from the model. Discriminated on type.
Known types: message, function_call, reasoning.
Unknown types from the provider are preserved verbatim.
Concatenated text output for convenience.
Whether parallel tool calls were enabled.
Tool choice setting used.
Tools that were available.
Token usage for a Response API request.
Error details if status is "failed".
Details if status is "incomplete".
Routing decision metadata included in successful responses. 10 STABLE fields (4 required + 6 optional) in the current public contract.