identity

proprietary
OpenAI logo

gpt-6.1-terraOpenAI

from /1M in$0.50openai
context1.1M128K out
providers26 regions
price spread2.4x7 endpoints
endpoints
7
regions
6
api
chat
released
October 2026
eu routing
available

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 2.4x more on microsoft azure ai than on openai. That is what the endpoints table is for.

endpoints

7 / 6 regions
Providers serving gpt-6.1-terra, with pricing and measured performance. Best value in each column is coloured.
#flags
1OpenAIGlobal1.1M$0.50$2.50$0.02no-train
2OpenAIGlobal1.1M$1.00$5.00$0.05no-train
3Microsoft Azure AIeastus1.1M$1.00$5.00$0.05zdr
4Microsoft Azure AIfrancecentral1.1M$1.20$6.00$0.06zdr
5Microsoft Azure AIgermanywestcentral1.1M$1.20$6.00$0.06zdr
6Microsoft Azure AIswedencentral1.1M$1.20$6.00$0.06zdr
7Microsoft Azure AIwesteurope1.1M$1.20$6.00$0.06zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Nov 2

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
SciCode55.1
Intelligence Index51.0
Humanity's Last Exam46.2
3 evalsmean50.8

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-10-26.

call it

model=
gpt-6.1-terra

requesty routes this id across every provider serving gpt-6.1-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.

quickstart

openai compatible
main.py
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-6.1-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

notes

reference

GPT-6.1 Terra, a fast, efficient model that combines detailed visual reasoning and precise computer use alongside clearer, more natural writing. A significant step up from GPT‑5.6 Terra, it excels at the communication and computer-based tasks that fill the workday, from drafting proposals and interpreting technical drawings to filling out forms and editing videos.

questions 6

Which providers serve gpt-6.1-terra?
gpt-6.1-terra is available from 2 providers through Requesty: OpenAI, Microsoft Azure AI. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does gpt-6.1-terra cost?
Pricing starts at $0.50 per million input tokens and $2.50 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is gpt-6.1-terra open weights?
No. gpt-6.1-terra is a proprietary model from OpenAI, served through OpenAI's own API and licensed cloud platforms.
What is the context window of gpt-6.1-terra?
gpt-6.1-terra supports up to 1.1M tokens of context, with up to 128K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use gpt-6.1-terra with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "gpt-6.1-terra" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call gpt-6.1-terra by its managed id or a provider id?
Use the managed id, "gpt-6.1-terra". Requesty picks which of the 2 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. There is also an EU-only id, "gpt-6.1-terra@eu", which routes the same way but only through EU-hosted providers. Send a provider id like "openai/gpt-6.1-terra:flex" only when you need one specific deployment and want no failover.

more from openai 6

Other OpenAI models
modelcontextfrom /Mproviders
gpt-6.1-sol1.1M$1.002
gpt-6-luna1.1M$0.052
gpt-6-sol1.1M$1.002
gpt-6-astra1.1M$5.002
gpt-5.6-luna1.1M$0.103
gpt-5.6-terra1.1M$1.003

route gpt-6.1-terra through one endpoint

One key for 2 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

gpt-6.1-terra2 providers7 endpointsfrom $0.50 /1M inctx 1.1Mspread 2.4xupdated Nov 2