Favicon for openai

OpenAI: GPT-6.1 Terra

openai/gpt-6.1-terra

GPT-6.1 Terra is the mid-tier model in OpenAI's GPT-6.1 series, priced below GPT-6.1 Sol. It is suited for everyday agentic, coding, and writing work, is particularly strong at understanding screenshots and on-screen content, and is efficient enough for high-volume workloads.

Modalities
In / out price
$1 / $5per 1M
Context
1.1M
Released
Oct 26, 2026

Providers

Different companies host the same model. OpenRouter routes your request to one of them based on the routing mode you pick: Balanced (price + speed), Nitro (fastest), or Floor (cheapest).

  • Not used in Standard routing:Why these endpoints are not used

Pricing

The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.

Weighted average

Input
$0.256/M tokens
Output
$5.079/M tokens
Price history
No effective price data for this selection
  • Not used in Standard routing:Why these endpoints are not used

Performance

Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).

Throughput
85tok/s

P50, best across providers

Latency
1.18s

P50, best provider

AutoExacto benchmarks
GPQA DiamondTAU-BenchOpenAI91.1%70.0%Azure (EU)91.9%68.7%Amazon Bedrock91.9%68.4%Azure90.9%69.3%Azure (US)90.1%65.3%

Uptime

Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.

Uptime (3d)The model was reachable. Request routed to a provider.
100.00%
Availability (3d)The model returned inference from any provider. Errors and empty responses count against it.
99.90%

Availability over the last 3 days

Last 72 hours
Availability 99.90%
3 Days Ago2 Days AgoYesterdayNow

Availability over the last 24 hours

OpenRouter Availability
99.91%
Without Routing
98.07%

When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and provider routing options.

Benchmarks

Scores on standardized evaluations and this model’s own outputs on shared benchmark prompts. Higher percentages are better — and each rank shows where this model lands among the models evaluated on that source.

Apps

Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.

1.
Favicon for https://openai.com/codex
Codex
314Btokens
2.
Favicon for https://nousresearch.com
Hermes Agent
244Btokens
3.
Favicon for https://omp.sh/
omp
new
135Btokens
4.
Favicon for https://pi.dev/
pi
114Btokens
5.
Favicon for https://claude.ai/apple-touch-icon.png
Claude Code
26.2Btokens
Rest of OpenRouter
101B
Top 5 Apps
34.6B

Activity

Token volume and request traffic to this model over time.

API

Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.

OpenAI: GPT Terra versions

Available through EU in-region routing

OpenAI: GPT-6.1 Terra is available through EU in-region routing. Requests sent to eu.openrouter.ai are decrypted in the EU and routed only to shared provider endpoints in Europe (the EU/EEA, the UK, and Switzerland).

Providers in Europe
Azure
Prices in Europe
  • Azure: $1.20/M tokens input, $6/M tokens output
Base URL
https://eu.openrouter.ai/api/v1
Plan
Requires Business or Enterprise. Self-serve on Business: no contract, no monthly minimum. OpenRouter Business for EU in-region routing

Fails closed: if no shared provider endpoint in Europe is available, the request errors instead of leaving the region. Requests served by your own BYOK key go to your deployment’s region, which you control. In-region routing docs

Frequently asked questions