GPT-5.6 Terra vs Sonar
At a Glance
| Compare | GPT-5.6 TerraOpenAI | SonarPerplexity |
|---|---|---|
| Intelligence, Cost, and Efficiency | ||
| IntelligenceHigher is better · MM Intelligence v2.5 | #13 of 4674.9 score · 3/3 sources · complete | UnrankedNot in the 46-model eligible cohort |
| CostLower is better · Published-token output estimate | #35 of 44$0.266 per LiveBench case | UnrankedNot in the 44-model eligible cohort |
| EfficiencyHigher is better · MM Efficiency v1.5 | #23 of 3851.5 score · 3/3 sources · complete | UnrankedNot in the 38-model eligible cohort |
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | $2.00Openai ↗ · Sep 3, 2026 | $1.00Openrouter ↗ · Sep 22, 2026 |
| Output priceFrom · USD / 1M tokens | $12.00Openai ↗ · Sep 3, 2026 | $1.00Openrouter ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | 1,050K | 128K |
| Model facts checked | Aug 28, 2026View model evidence → | Aug 29, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | GPT-5.6 Terra | Sonar |
|---|---|---|
| Developer | OpenAI | Perplexity |
| Family | Gpt 5 6 | Sonar |
| Model | GPT-5.6 Terra | Sonar |
| Version | GPT-5.6 Terra | Sonar |
| Lifecycle | active | active |
| Released | Unknown | Unknown |
| Knowledge cutoff | 2026-02-16 | Unknown |
| Input modalities | Text, Image | Text |
| Output modalities | Text | Text |
| Context window | 1,050K | 128K |
| Total parameters | Unknown | Unknown |
| Active parameters | Unknown | Unknown |
| License | Unknown | Unknown |
| Open weights | No | No |
| API available | Yes | Yes |
| Self-hostable | No | No |
| Provider access | Openai (Standard), Openrouter (Standard) | Openrouter (Standard), Perplexity (Standard) |
| Capabilities | chat, generation, reasoning, tools | chat, citations, search |
GPT-5.6 Terra Capabilities
Sonar Capabilities
Primary Evidence
Sources and Freshness
Questions
GPT-5.6 Terra vs Sonar FAQs
Is GPT-5.6 Terra or Sonar better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both GPT-5.6 Terra and Sonar, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, GPT-5.6 Terra or Sonar?+
GPT-5.6 Terra is $2.00 and Sonar is $1.00 per million tokens, so Sonar is cheaper on this metric. GPT-5.6 Terra is $12.00 and Sonar is $1.00 per million tokens, so Sonar is cheaper on this metric.
Which has a larger context window, GPT-5.6 Terra or Sonar?+
GPT-5.6 Terra has the larger sourced context window. GPT-5.6 Terra supports 1,050K and Sonar supports 128K.
Which performs better in benchmarks, GPT-5.6 Terra or Sonar?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can GPT-5.6 Terra or Sonar be self-hosted?+
Both models have the same recorded self-hosting status: unsupported. GPT-5.6 Terra is not marked open weight; Sonar is not marked open weight.
Can GPT-5.6 Terra and Sonar understand images?+
GPT-5.6 Terra is documented with image input; Sonar is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, GPT-5.6 Terra or Sonar?+
Neither has a larger sourced maximum output. GPT-5.6 Terra is 128K and Sonar is —.
Do GPT-5.6 Terra and Sonar support reasoning and tool use?+
GPT-5.6 Terra: reasoning, tool calling, and image input. Sonar: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, GPT-5.6 Terra or Sonar?+
GPT-5.6 Terra has 2 sourced provider routes; Sonar has 2, a tie.
Which offers better value, GPT-5.6 Terra or Sonar?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.