gpt-5.6-terraOpenAI
- endpoints
- 10
- regions
- 9
- best tok/s
- 141
- api
- chat
- released
- July 2026
- eu routing
- available
capabilities 5/8
The same weights cost 2.2x more on microsoft azure ai than on openai. That is what the endpoints table is for.
| # | flags | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1 |  OpenAI | Global | 1.1M | $1.00 | $6.00 | $0.10 | 1.88s | 73.0 | no-train | |
| 2 | OpenAI | Global | 1.1M | $2.00 | $12.00 | $0.20 | 1.88s | 73.0 | no-train | |
| 3 |  Microsoft Azure AI | eastus2 | 1.1M | $2.00 | $12.00 | $0.20 | 1.83s | 89.0 | zdr | |
| 4 | Microsoft Azure AI | francecentral | 1.1M | $2.20 | $13.20 | $0.22 | 1.83s | 89.0 | zdr | |
| 5 | Microsoft Azure AI | germanywestcentral | 1.1M | $2.20 | $13.20 | $0.22 | 1.83s | 89.0 | zdr | |
| 6 | Microsoft Azure AI | swedencentral | 1.1M | $2.20 | $13.20 | $0.22 | 1.83s | 89.0 | zdr | |
| 7 | Microsoft Azure AI | westeurope | 1.1M | $2.20 | $13.20 | $0.22 | 1.83s | 89.0 | zdr | |
| 8 |  AWS Bedrock | us-east-1 | 1.1M | $2.20 | $13.20 | $0.22 | 2.19s | 141.0 | - | zdr |
| 9 | AWS Bedrock | us-east-2 | 1.1M | $2.20 | $13.20 | $0.22 | 2.19s | 141.0 | - | zdr |
| 10 | AWS Bedrock | us-west-2 | 1.1M | $2.20 | $13.20 | $0.22 | 2.19s | 141.0 | - | zdr |
| provider | now | low | high | change |
|---|---|---|---|---|
| Microsoft Azure AI | 1.83s | 712ms | 3.07s | +208% |
| OpenAI | 1.88s | 832ms | 3.66s | +172% |
| AWS Bedrock | 2.19s | 1.59s | 3.42s | +87% |
median wait before the first token lands. this is the number a user feels, and it moves with provider load through the day.
Lines are steps: each sample is one week of traffic held flat, not a slide from the week before. Click a name in the key to drop it from the plot. Measured through Nov 2.
no published benchmark scores for this model
gpt-5.6-terrarequesty routes this id across every provider serving gpt-5.6-terra, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it
Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.
from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create( model="gpt-5.6-terra", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ],) print(response.choices[0].message.content)
Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models
GPT-5.6 Terra is OpenAI's balanced frontier model for everyday production workloads, delivering near flagship reasoning, coding, and agentic performance at roughly half the cost of the previous generation. It features a 1M+ token context window with support for text and image inputs, server side tool calling, and prompt caching.
questions 7
Which providers serve gpt-5.6-terra?
How much does gpt-5.6-terra cost?
Is gpt-5.6-terra open weights?
What is the context window of gpt-5.6-terra?
Which provider is fastest for gpt-5.6-terra?
How do I use gpt-5.6-terra with the OpenAI SDK?
Should I call gpt-5.6-terra by its managed id or a provider id?
more from openai 6
| model | context | from /M | providers |
|---|---|---|---|
| gpt-6.1-terra | 1.1M | $0.50 | 2 |
| gpt-6.1-sol | 1.1M | $1.00 | 2 |
| gpt-6-luna | 1.1M | $0.05 | 2 |
| gpt-6-sol | 1.1M | $1.00 | 2 |
| gpt-6-astra | 1.1M | $5.00 | 2 |
| gpt-5.6-luna | 1.1M | $0.10 | 3 |
route gpt-5.6-terra through one endpoint
One key for 3 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology