Kimi K3 is now availableExplore Kimi K3
GPT-5.6 API Status: OpenAI GA, Model IDs, and EvoLink Route Checklist
Release Watch

GPT-5.6 API Status: OpenAI GA, Model IDs, and EvoLink Route Checklist

EvoLink Team
EvoLink Team
Product Team
June 20, 2026
Updated on July 11, 2026
5 min read
Update, July 11, 2026: GPT-5.6 is no longer a preview-only story. OpenAI announced GPT-5.6 general availability on July 9, 2026, and the API docs now list the GPT-5.6 family with gpt-5.6, gpt-5.6-sol, gpt-5.6-terra, and gpt-5.6-luna.
For EvoLink users, the practical answer is: treat GPT-5.6 as a live model family, but still verify account access, route pricing, cache behavior, rate limits, and fallback behavior before moving production traffic.

Quick Status

QuestionCurrent statusWhat it means for you
Is GPT-5.6 official?Yes. OpenAI GA was announced on July 9, 2026.You can plan production adoption instead of preview-only experiments.
Is it one model?No. GPT-5.6 is a family: Sol, Terra, and Luna.Route by workload instead of hard-coding one tier everywhere.
What does gpt-5.6 mean?OpenAI lists it as an alias to gpt-5.6-sol.Use the alias only when Sol is intentionally the default.
Is GPT-5.6 live on EvoLink?Yes. The GPT-5.6 route is live.Confirm pricing and account access in your EvoLink dashboard before scaling traffic.
Which tier should I pick?Depends on your workload.Use the Sol vs Terra vs Luna routing guide for model choice.

Confirmed Model IDs

OpenAI model IDTierUse when
gpt-5.6Alias to SolYou want the GPT-5.6 flagship behavior and accept Sol-level cost.
gpt-5.6-solFlagshipFrontier reasoning, hard coding tasks, deep research, long-horizon agents.
gpt-5.6-terraBalancedEveryday production traffic where quality, latency, and cost all matter.
gpt-5.6-lunaCost-efficientHigh-volume, low-latency, budget-controlled workloads.
In practice, you rarely need to treat Sol, Terra, and Luna as three separate products. The model IDs above are the only integration difference — the real question is still which GPT-5.6 tier fits each workload.

Pricing Boundary

OpenAI list pricing is:

TierInput / 1M tokensOutput / 1M tokensProduction note
Sol$5.00$30.00Use for high-value reasoning and agentic tasks.
Terra$2.50$15.00Test as the default production candidate.
Luna$1.00$6.00Use for high-volume tasks when quality is sufficient.

Do not copy these values into customer-facing EvoLink quotes without checking EvoLink route pricing, account terms, cache discounts, retries, and actual successful-task cost.

What Still Needs Verification Before Production

AreaWhy it matters
EvoLink route pricingOpenAI list price is not always the same as platform route pricing.
Account accessAvailability can vary by account, region, or provider-side permissions.
Cache billingGPT-5.6 workloads may depend heavily on cached input economics.
Rate limitsSol, Terra, and Luna can need different rollout limits.
Fallback behaviorProduction traffic should not depend on one new route without a rollback path.
Request surfaceConfirm supported endpoints, streaming, tools, and reasoning controls against EvoLink docs before publishing code examples.
If your question is "is GPT-5.6 real and what are the model IDs?", this status page answers it. If your question is "which tier should I use?", read the GPT-5.6 Sol vs Terra vs Luna routing guide.
For hands-on testing, start from the GPT-5.6 model page, create an EvoLink API key, and run a small evaluation matrix before switching default production traffic.

Official Sources

FAQ

Is GPT-5.6 generally available?

Yes. OpenAI announced GPT-5.6 general availability on July 9, 2026.

What is the GPT-5.6 model ID?

OpenAI lists gpt-5.6 as an alias to gpt-5.6-sol. The tier-specific model IDs are gpt-5.6-sol, gpt-5.6-terra, and gpt-5.6-luna.

EvoLink now positions GPT-5.6 as a live model route. Before production rollout, verify account access, pricing, limits, and fallback behavior inside EvoLink.

How much does GPT-5.6 cost?

OpenAI list pricing is $5/$30 for Sol, $2.50/$15 for Terra, and $1/$6 for Luna per 1M input/output tokens. EvoLink route pricing should be confirmed before quoting customers.

Should teams migrate from GPT-5.5 immediately?

Not blindly. Keep GPT-5.5 as a baseline and fallback while testing GPT-5.6 Sol, Terra, and Luna on real workloads.

Which GPT-5.6 tier should be default?

Terra is the most natural default candidate for balanced production traffic, but each team should benchmark Sol, Terra, and Luna against task value, latency, and cost.

Should code examples hard-code gpt-5.6-sol?

Only when Sol is intentionally required. Otherwise keep model choice configurable so teams can route between Sol, Terra, Luna, and fallbacks without code changes.

Ready to Reduce Your AI Costs by 89%?

Start using EvoLink today and experience the power of intelligent API routing.