In one sentence: OpenAI did not drop a single "GPT-6" — it launched three new names at once, Sol, Terra, and Luna, with three price lines sitting side by side on the pricing page, and the first question most people ask is how these three should divide the work so money is not wasted. Below we start from this new naming logic and walk through tier specs, benchmark gaps, ChatGPT/Codex subscription access, and how developers should write routing code — as an actionable checklist.
If token billing is still fuzzy, start with our AI token pricing comparison; if you were waiting for an integer-generation GPT-6, GPT-6 release date prediction explains why you may not need to wait.
Why three models instead of one "GPT-6"?
On July 9, 2026, OpenAI released the full GPT-5.6 family: flagship Sol, balanced Terra, and value-tier Luna. Sol had already opened in a limited preview for trusted partners on June 26. This is not "one model, three skins" — it is a naming shift: the number (5.6) marks the generation; Sol / Terra / Luna mark capability tiers that can evolve on their own. A future upgrade might refresh only Terra or Luna while Sol stays put, so the three product lines are no longer locked to a single release cadence.
For buying decisions, that matters more than it sounds. "Should we upgrade?" used to be a single choice; now it is "which line upgrades to which version?" The good news: all three tiers accept the same input format, tool protocol, and context window — switching models is basically changing one string, not rewriting prompts or tool definitions.
Separate "three products" from "three entry points"
Sol / Terra / Luna are model tiers; ChatGPT, ChatGPT Work / Codex, and the OpenAI API are three different access channels. The same tier does not open identically on every channel — see ChatGPT subscription access below for channel-by-channel rules.
Sol / Terra / Luna at a glance: specs and pricing
Context window, max output length, and tool support (function calling, web search, file search, computer use) are identical across tiers. The hard differences are price and reasoning efficiency — so the core variable is "is this task worth several times the per-token rate," not "which model supports the feature I need."
| Model | API model ID | Input / output (per 1M tokens) | Context / max output | Positioning |
|---|---|---|---|---|
| GPT-5.6 Sol | gpt-5.6-sol (alias gpt-5.6) |
$5 / $30 | 1.05M / 128K | Complex coding, research, high-stakes long tasks |
| GPT-5.6 Terra | gpt-5.6-terra |
$2.50 / $15 | 1.05M / 128K | Daily Agent loops, value baseline |
| GPT-5.6 Luna | gpt-5.6-luna |
$1 / $6 | 1.05M / 128K | High-concurrency classification, extraction, reviewable drafts |
OpenAI's reference frame is GPT-5.5: Terra is positioned as "match or beat GPT-5.5 performance at lower cost," while Luna is the faster, cheaper entry tier. If you still run GPT-5.5 as a baseline, swapping to Terra is likely a free upgrade — same or better performance, lower bill — as long as you re-run your own eval set to confirm no behavior drift.
One diagram: routing from task intake to execution
Signals to upgrade to Sol
- Task spans multiple files, needs multi-step planning and self-correction
- Needs computer use to verify rendered output
- Security review, complex debugging, research-grade reasoning
- High failure cost — worth paying several times the unit rate for success
Signals to downgrade to Luna
- Fixed input structure; output quickly verifiable by rules or humans
- High-concurrency classification, field extraction, tagging
- Reliable grader already in place for review
- Volume over quality; unit price sensitive
Benchmarks: what the premium buys you
OpenAI's published scores span coding, knowledge work, browsing, and safety. Below are results most relevant to tier choice (official evals — validate on your own task sets before committing):
| Benchmark | Sol | Terra | Luna | GPT-5.5 |
|---|---|---|---|---|
| Artificial Analysis Coding Agent Index | 80.0 (new SOTA) | 77.4 | 74.6 | 76.4 |
| Agents' Last Exam (long-horizon professional tasks) | 52.7% | 50.4% | 50.3% | 46.9% |
| OSWorld 2.0 (computer use) | 62.6% | 50.2% | 45.6% | 47.5% |
| SEC-Bench Pro (security testing) | 71.2% | 57.7% | 48.9% | 45.8% |
Two patterns stand out: on coding and long-horizon professional tasks, gaps among the three tiers are modest — Terra and Luna already match or beat GPT-5.5, so most daily Agent loops do not need Sol's premium. But on computer use and security testing — tasks that need multi-turn self-correction and fine-grained control — Sol pulls much further ahead, which maps to "high failure cost, must verify execution" scenarios and explains why Sol costs 5× Luna's output rate.
Do not judge on a single benchmark percentage
OpenAI also stresses that Sol reaches higher scores with fewer output tokens and less time — a higher unit price does not always mean a higher total bill. Evaluate "cost per successful task," not per-1M-token list price, especially when tasks need multiple retries.
Consumer choice: ChatGPT subscription access
Main ChatGPT, ChatGPT Work / Codex, and the developer API do not share identical access rules — easy to mix up:
| Channel / plan | Available models | Notes |
|---|---|---|
| ChatGPT · Plus / Pro / Business / Enterprise | Sol (medium / high reasoning effort) | Pro and Enterprise also get Sol Pro for highest-quality complex work |
| ChatGPT Work / Codex · Free / Go | Terra | Free tier has no manual Sol / Luna switching |
| ChatGPT Work / Codex · Plus and above | Sol / Terra / Luna — any tier | Set reasoning effort (effort) per task |
| max reasoning effort | All Work / Codex users with GPT-5.6 access | Enable manually in settings — slower but more thorough |
| ultra (multi-Agent parallel) | Work: Pro / Enterprise; Codex: Plus and above | Defaults to 4 parallel Agents — higher token spend for faster, stronger results |
For occasional ChatGPT Q&A, Sol at medium effort on Plus is enough. If Codex is your daily coding partner, run Terra as the baseline and switch to Sol for cross-file refactors or production incident root-cause work — not the most expensive tier all day.
Developer choice: model IDs, caching, and routing code
The most common API pitfall is treating the gpt-5.6 alias as a fixed version — it routes to gpt-5.6-sol by default and will drift as upgrades land. In production, use full model IDs:
# Pick model by task type and failure cost — don't default to flagship def pick_model(task: str, blast_radius: str = "low") -> tuple[str, str]: if blast_radius == "high" or task in ("security_review", "multi_file_refactor"): return "gpt-5.6-sol", "high" # High failure cost — max reasoning effort if task in ("ticket_tagging", "field_extraction", "draft_for_review"): return "gpt-5.6-luna", "medium" # Fixed structure, human review as backstop return "gpt-5.6-terra", "medium" # Default baseline — enough for most Agent loops
Log the chosen model, reasoning effort, tool calls, token usage, and final score in one place — otherwise routing has no data to iterate on. That aligns with our OpenRouter real usage rankings guidance: routing is a runtime policy, not a constant baked into code.
Caching billing changed — update your cost model
GPT-5.6 introduces explicit cache breakpoints and a 30-minute minimum cache lifetime: cache writes bill at 1.25× uncached input price; cache hits still get a 90% read discount. Put stable system prompts, schemas, and reference material early in the prompt with cache breakpoints to cut real Agent cost when context repeats — but if every request changes, breakpoints add complexity with no savings.
Two more capabilities worth tracking: Programmatic Tool Calling (in the Responses API, the model writes a short program to coordinate multiple tool calls and filter intermediate results, reducing large round-trip payloads — compatible with zero data retention ZDR); and multi-Agent parallel (beta), the mechanism behind ultra. Benchmark both on a single data-heavy workflow before replacing direct tool calls, and keep a single-Agent fallback path.
6 real scenarios — which tier fits
| Scenario | Recommended tier | Why |
|---|---|---|
| Support ticket classification / field extraction | Luna | Fixed input structure; quickly verifiable by rules or humans |
| Daily coding Agent (edit code + run tests) | Terra | Coding scores near or above GPT-5.5 at half of Sol's price |
| Cross-file refactor / production incident root cause | Sol | High failure cost; needs multi-step planning and self-correction |
| Long documents / contract summaries (hundreds of thousands of input tokens) | Start with Terra; escalate to Sol if precision falls short | All tiers share 1.05M context, but Sol retrieves more reliably at long context |
| Security assessment / penetration test report generation | Sol (Trusted Access required) | Largest cyber benchmark gap across tiers; full capability needs verified account |
| Batch content drafts (human review follows) | Luna | "Drafts always get reviewed" is OpenAI's canonical Luna use case |
Safety gate: a Cyber access deadline not to miss
Under OpenAI's Preparedness Framework, Sol, Terra, and Luna are rated "High" (not "Critical") on tracked cybersecurity and bio/chemical categories — with the strictest guardrails to date. OpenAI reports Sol's cyber safety filters block roughly 10× more potentially harmful activity than the prior generation.
For security research, red team, and patch-validation teams, one hard date: personal accounts must enable Advanced Account Security with a hardware passkey (e.g. Yubico) before September 1, 2026 to keep full access to frontier cyber-capable models; accounts without it fall back to default access. Enterprise teams apply separately through Trusted Access for Cyber.
- Individuals — verify identity and apply for Trusted Access early; configure a hardware passkey before September 1
- Teams / enterprise — plan the security-team application workflow ahead of launch day
- General developers — no action needed for non offensive-security work; normal API calls are unaffected
Common mistakes
- "Expensive is always right" — on coding and long-horizon tasks, Terra and Luna already match or beat GPT-5.5; running Sol everywhere is often waste.
- "Use the
gpt-5.6alias for convenience" — the alias drifts with upgrades; pin full model IDs in production. - "Bigger context means skip retrieval" — 1.05M context is an option, not a goal; Luna's retrieval quality lags Sol / Terra at long context — do not blindly fill the window.
- "Add cache breakpoints everywhere" — on requests that change every time, breakpoints only add 1.25× write cost with no benefit.
- "More Agents in ultra is always better" — multi-Agent parallel is still beta; start with single-Agent plus a reliable grader, then decide if parallel is worth the extra tokens.
FAQ
When was GPT-5.6 released? Did all three models launch at once? Sol opened in a limited preview on June 26, 2026. Sol, Terra, and Luna reached general availability on July 9 across ChatGPT, Codex, and the API, rolling out globally within the following 24 hours.
Which model does the gpt-5.6 API alias point to by default? It routes to gpt-5.6-sol. For fixed behavior, use full model IDs so the alias cannot drift on future upgrades.
Are Terra and Luna cut-down versions of Sol? No. They are independently evolving capability tiers — a future generation might upgrade only Terra or Luna. Today Terra beats GPT-5.5 on coding / browsing benchmarks; Luna is best value but trails on very long context and hard research problems.
Can free-tier ChatGPT users access GPT-5.6? Main ChatGPT free tier still uses older or rate-limited models. ChatGPT Work / Codex Free / Go can use Terra. Sol needs Plus or above with higher reasoning effort.
If budget allows only one model, which should I pick? Start with Terra — OpenAI's daily value baseline, half of Sol's price with near or above GPT-5.5 performance. Reserve Sol for high-stakes work and Luna for large-batch tasks with automated grading; three-tier routing usually beats a single-model bet.
- GPT-6 Release Date Prediction: When Will It Launch? Pricing, Features & API Analysis
- What Is a Token? 2026 AI Model Pricing Comparison
- OpenRouter Real Usage Rankings 2026
- GPT-5.5-Codex Install & Usage Guide (2026)
- Claude Fable 5 vs Opus 4.8 vs Gemini 3.5 Flash Benchmark Comparison
ZavCloud
Run model routing and evals on stable hardware
Compare Sol / Terra / Luna, run Codex CI, batch benchmarks — dedicated Mac mini M4 cloud hosts by the day, fixed IPv4 and 1 Gbps egress, eval results unaffected by shared compute contention.
View Cloud Mac plans