Model comparison
GPT-5.6 Sol vs GPT-5.6 Terra
Compare GPT-5.6 Sol vs GPT-5.6 Terra API pricing: input/output token costs, cache pricing, context windows, workload estimates, and routing fit.
GPT-5.6 Sol
openai · gpt-5.6-sol
- Input
- $5
- Output
- $30
- Context
- 1.1M
GPT-5.6 Terra
openai · gpt-5.6-terra
- Input
- $2.5
- Output
- $15
- Context
- 1.1M
Quick take
GPT-5.6 Terra has the lower input price at $2.5 per 1M input tokens. GPT-5.6 Terra is cheaper for the example blended workload below. GPT-5.6 Sol has the larger context window at 1.1M tokens.
Choose GPT-5.6 Sol if...
- GPT-5.6 Sol is a reasonable pick when its provider, latency, or integration path fits your stack better.
Choose GPT-5.6 Terra if...
- GPT-5.6 Terra is the better default for cost-sensitive traffic and repeated high-volume calls.
Example workload cost
Estimates use input tokens plus 20% output tokens. They exclude provider discounts, cache hits, and tool/search surcharges.
| Workload | GPT-5.6 Sol | GPT-5.6 Terra | Cheaper |
|---|---|---|---|
| 1M input + 200K output | $11.00 | $5.50 | GPT-5.6 Terra |
| 10M input + 2M output | $110.00 | $55.00 | GPT-5.6 Terra |
| 100M input + 20M output | $1,100.00 | $550.00 | GPT-5.6 Terra |
Context, output, and capability fit
GPT-5.6 Sol provides the larger context window. Check max output separately when the task needs long reports, code generation, or full-document rewrites.
- GPT-5.6 Sol max output
- 128K
- GPT-5.6 Terra max output
- 128K
- GPT-5.6 Sol features
- prompt caching, function calling, vision
- GPT-5.6 Terra features
- prompt caching, function calling, vision
Risk notes for GPT-5.6 Sol
- High output price: cap max tokens for verbose generation workloads.
Risk notes for GPT-5.6 Terra
- No major capability risk is flagged in this snapshot, but provider pages should still be verified before production routing.
Routing tags
frontierpremiumreasoningcodingagentslong-contextmultimodalcache-friendlyrag