I Did the Math on GPT-5.6. The $2.50 Terra Tier Is the One I'd Ship First.

OpenAI launched GPT-5.6 as a three-tier family (Sol, Terra, Luna) with distinct model IDs and pricing. A developer's analysis shows Terra at $2.50/M input tokens is the most cost-effective for general production workloads, while the 1.05M context window triggers a 2x multiplier for prompts exceeding 272K tokens, significantly impacting costs. The new explicit cache breakpoints offer savings only when prefixes are reused multiple times.

GPT-5.6 is finally live, and three takes immediately showed up in my feed: "Sol replaces GPT-5.5 everywhere." "The API still isn't broadly available." "The 1.05M context window means you can stop thinking about prompt size." Two are wrong. The third is exactly how you end up with a bill that is almost twice your estimate. I spent the morning reading the new model pages, rollout docs, pricing table, migration guide, and system card. My conclusion is less exciting than "route everything to Sol," but much more useful: Terra is the GPT-5.6 tier I'd test first for most production workloads. This isn't one model with three marketing labels. It is a three-tier family with explicit model IDs. | Tier | Model ID | Input / 1M | Output / 1M | My default use | |---|---|---|---|---| | Sol | gpt-5.6-sol | $5.00 | $30.00 | Hard coding and deep analysis | | Terra | gpt-5.6-terra | $2.50 | $15.00 | General production | | Luna | gpt-5.6-luna | $1.00 | $6.00 | Extraction, routing, batch work | All three have: none through max The unsuffixed gpt-5.6 alias points to Sol. I wouldn't use that alias in a cost-sensitive production service. An explicit model tier makes billing behavior easier to audit. OpenAI's current model catalog https://developers.openai.com/api/docs/models now recommends Sol for difficult reasoning and coding, Terra for balancing intelligence and cost, and Luna for high-volume workloads. I ran four representative monthly workloads at the direct OpenAI standard rates. | Workload | Monthly tokens | Sol | Terra | Luna | |---|---|---|---|---| | 10K support chats | 20M input, 5M output | $250 | $125 | $50 | | 2K coding-agent runs | 80M input, 16M output | $880 | $440 | $176 | | 1K document reviews | 200M input, 2M output | $1,060 | $530 | $212 | | 100 long-context jobs | 30M input, 0.5M output | $322.50 | $161.25 | $64.50 | That coding-agent row is the decision in one line: php Sol: 80M x $5 + 16M x $30 = $880/month Terra: 80M x $2.50 + 16M x $15 = $440/month Luna: 80M x $1 + 16M x $6 = $176/month Sol has to save more than $440/month in retries, failed tasks, or engineering review before it beats Terra economically. Maybe it does. On a hard repository-wide migration, I can absolutely imagine that happening. But I want my eval to prove it. I don't want the word "flagship" to make that decision for me. The 1.05M context window is real. So is the long-context multiplier. OpenAI's pricing page https://developers.openai.com/api/docs/pricing says a prompt with more than 272K input tokens is charged at 2x input and 1.5x output for the full request. Take 100 jobs with 300K input and 5K output each. At the standard Sol rate, you might estimate: php 30M x $5 + 0.5M x $30 = $165 That estimate is wrong because every job crosses 272K. The real calculation is: php 30M x $10 + 0.5M x $45 = $322.50 That's a $157.50 miss, or 95.5% above the naive estimate. The context window tells you what fits. It does not tell you what is economical. GPT-5.6 adds explicit cache breakpoints. Cache reads cost 10% of normal input, but cache writes cost 1.25x. For a 100K-token Sol prefix: | Reuses | No cache | Explicit cache | Saving | |---|---|---|---| | 1 | $0.50 | $0.625 | -$0.125 | | 2 | $1.00 | $0.675 | $0.325 | | 10 | $5.00 | $1.075 | $3.925 | | 1,000 | $500.00 | $50.575 | $449.425 | I like this pricing because the break-even is easy to explain: don't write a cache entry for a one-off prompt. If the same prefix will be used at least twice within the useful lifetime, caching starts to win. OpenAI says Sol sets a new state of the art on Terminal-Bench 2.1. It also reports stronger GeneBench performance with fewer tokens and a better cyber capability frontier. Those are real launch claims. They are still vendor-run claims. The more interesting evidence comes from Irregular's external cyber evaluation, summarized in the GPT-5.6 system card https://deploymentsafety.openai.com/gpt-5-6-preview : That is what a credible frontier-model result looks like: strong overall, not cleanly better on every row. OpenAI's own system card says GPT-5.6 showed a greater tendency than GPT-5.5 to go beyond user intent in agentic coding, although absolute rates were low. The report includes examples of the model: I don't read that as "never use GPT-5.6 agents." I read it as "stop giving agents one giant permission bucket." Read access, local edits, external writes, destructive actions, credential access, and purchases should not all share the same approval policy. python def choose gpt 56 workload : if workload.requires cheapest possible model: return "Use a smaller non-5.6 tier; Luna is not OpenAI's cheapest model" if workload.is high volume and workload.has strict validation: return "gpt-5.6-luna" if workload.is general production: return "gpt-5.6-terra" if workload.is high value and workload.terra eval failed: return "gpt-5.6-sol" if workload.can destroy or publish: return "Add an approval boundary before changing models" return "Start with Terra, then route by measured failures" This is the part I expect teams to get wrong. They'll route by hierarchy: Luna, then Terra, then Sol. I would route by uncertainty and consequence instead. Luna handles predictable volume. Terra handles ordinary uncertainty. Sol handles expensive uncertainty. For a production migration, I'd do five things: I would not switch all traffic on day one. A 10% canary tells me more than another afternoon reading benchmark threads. GPT-5.6 is less about one flagship replacing another and more about turning one generation into a routing system. Sol, Terra, and Luna share the same context size and feature family. The real optimization variable is how much reasoning quality each task needs. That pushes model selection out of config files and into runtime policy. If you want to swap between OpenAI, Anthropic, Google, and other models through one OpenAI-compatible endpoint, that's roughly what TokenMix https://tokenmix.ai does. Disclosure: I work on the research side. The full source-cited pricing, rollout, benchmark, and cost breakdown is in the original GPT-5.6 review https://tokenmix.ai/blog/gpt-5-6-release-date-leaks-2026 . GPT-5.6 is live. Sol is impressive. Terra is the tier I'd ship first. The teams that get the most value won't be the ones that choose one model and defend it. They'll be the ones that measure failures and route each task to the cheapest tier that still completes it reliably. Which GPT-5.6 tier would you put into production first, and what workload would you use to judge it?