GPT-5.6 Model Selection Guide (2026): Sol, Terra, or Luna?

The GPT-5.6 family splits into three price-capability tiers, but "which tier" isn't a gut call. This article gives you an executable method: fix the tier by workload, tune depth with reasoning.effort, then use a cost formula and self-assessed routing to keep the bill low.

1. The three tiers at a glance (2026-08)

All three share: 1.05M context, 128K output, knowledge cutoff 2026-02-16, native multimodal input (text/image/audio/file).

2. The framework: workload first

Don't ask "which model should I buy". Ask "which category is my task":

1. High-volume small tasks (classification, extraction, summarization, routing, translation) → Luna + effort: "none". High volume, low price, quality is enough.
2. Day-to-day product load (chat, writing, doc Q&A, RAG generation) → Terra + effort: "medium". The quality/cost balance point.
3. Complex professional tasks (long code, multi-step agents, deep analysis, complex JSON generation) → Sol + effort: "high" or "xhigh".
4. Must-get-it-right tasks (math contests, code correctness verification, research analysis) → switch to o-series, effort fixed at max.

The rule of thumb: effort first, then tier; cheap first, then expensive.

3. reasoning.effort: a cheaper knob than upgrading tiers

Within a tier, reasoning.effort decides "how deep to think":

Experience: before upgrading tiers, raise effort from low to high on complex tasks — quality often jumps while the price delta is far smaller than a tier upgrade. Upgrade the tier only when "effort maxed out" still isn't enough.

4. Cost math: one formula

Per-call cost = input_tokens × input_price + output_tokens × output_price (per MTok)

Example: 1M input + 0.1M output tokens/day.

Same load, Sol costs 5× Luna. Three levers to save: route by task tier, effort: "none" for batch work, and Prompt Caching for repeated prefixes.

5. Dynamic routing: don't pay flagship prices for all traffic

Use self-assessment plus thresholds to auto up/down-grade:

1. Route by rule first: batch jobs → Luna, user interactions → Terra.
2. For "possibly complex" requests, let Terra answer at low effort and attach a self-assessed confidence.
3. When confidence falls below a threshold (say < 0.7), re-run once with Sol + effort: "high".

Only the few "not sure" requests hit the most expensive tier, so site-wide cost stays far below a blanket-Sol setup.

6. The o-series boundary

The correct way to use o-series:

• Use it (must get it right): math contests, code correctness verification, research-grade reasoning.
• Don't use it (everyday): chat, writing, summarization, RAG — slower and pricier with little payoff.

GPT-5.6 covers 95%+ of production load. o-series is a complement, not the default.

7. Common mistakes and troubleshooting

• Blanket Sol for everything → 5× the cost; split by workload and tune effort first.
• o-series as the default → slow, expensive, negative ROI on everyday tasks.
• Using messages in the Responses API → use the input field.
• Estimating with old output limits → the current ceiling is 128K output / 1.05M context; don't design requests around legacy caps.

8. What's Next

• The Complete Guide to GPT Models: GPT-5.6 Sol, Terra, Luna — full companion model list and migration paths
• OpenAI API Getting Started: Your First GPT-5.6 Call
• OpenAI Models Release Notes (2026, Living Document) — synced with the official changelog