Skip to main content
GPT 6.1 Terra is suited to interpreting product images and technical drawings, drafting text, and focused coding tasks. It is a separate model from GPT 5.6 Terra and GPT 6.1 Sol.

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 are none, 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.
Tool calling requires Responses, even when reasoning is set to none. Do not attach tools or tool_choice to this model in Chat Completions. For tool workflows, use a route that supports 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

Set MIXROUTE_API_KEY to your MixRoute API key. These examples use low effort without tools.

Request Fields

Responses Integration

On a MixRoute route with Responses support, use input, reasoning.effort, and max_output_tokens instead of the Chat Completions fields:
Responses function tools use top-level 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