Model Information
The sizes above are provider specifications. Effective limits, availability, pricing, Responses access, and hosted tools depend on the MixRoute route; model availability alone does not enable every upstream tool.
Reasoning and Tool Calling
Supported effort levels arenone, low, medium (default), high, xhigh, and max. none disables reasoning; minimal is not a supported level for this model.
Use top-level reasoning_effort in Chat Completions and nested reasoning.effort in Responses.
When effort is not none, omit temperature, top_p, and top_logprobs; also omit Chat Completions logprobs and Responses include: ["message.output_text.logprobs"].
Chat Completions Examples
SetMIXROUTE_API_KEY to your MixRoute API key. These examples use low effort without tools.
- cURL
- Python
Request Fields
Responses Integration
On a MixRoute route with Responses support, useinput, reasoning.effort, and max_output_tokens instead of the Chat Completions fields:
name, description, and parameters, not a nested function object. Your application executes returned calls and sends function_call_output with the matching call_id.
Preserve all returned output items required for the next turn, including reasoning items. Hosted computer-use and other tools need separate route support and application integration; changing the model ID alone does not enable them.
Chat Completions reference · Responses reference