Skip to main content

OpenAI GPT-5.6

Use this guide to adopt the GPT-5.6 family safely in production. GPT-5.6 is the current OpenAI GPT family for complex production workflows. In Phaseo, the fixed tier IDs map to the OpenAI model IDs gpt-5.6-sol, gpt-5.6-terra, and gpt-5.6-luna.

Migration quickstart

  1. Choose the fixed Sol, Terra, or Luna model that matches the workload.
  2. Swap only the model ID and keep the rest of the request stable.
  3. Re-test reasoning effort, structured outputs, tools, latency, and task cost.
  4. Canary the new route with your previous GPT-5 model available as a fallback.

Choose a model

OpenAI’s gpt-5.6 alias routes to gpt-5.6-sol. In Phaseo, use openai/gpt-5.6 or openai/gpt-sol-latest when you want that Sol-tier default, and use the fixed tier IDs for controlled routing. Phaseo also tracks tier aliases for the latest model in each tier: openai/gpt-sol-latest, openai/gpt-terra-latest, and openai/gpt-luna-latest. Use the fixed GPT-5.6 IDs for controlled migrations, and use the tier aliases only when you deliberately want future Sol, Terra, or Luna releases to roll forward through the same route.

What’s new

  • GPT-5.6 adds the new Sol/Terra/Luna split instead of one default GPT route.
  • All three GPT-5.6 tiers support reasoning.effort: "max" for the highest reasoning budget.
  • GPT-5.6 supports reasoning.mode: "pro" without switching to a separate Pro model slug.
  • GPT-5.6 adds persisted reasoning controls through reasoning.context.
  • GPT-5.6 adds beta multi-agent support and Programmatic Tool Calling for eligible tool-heavy workflows.
  • Prompt caching is priced with separate uncached input, cache read, cache write, and output meters.
  • Explicit prompt caching is supported through cache breakpoints and prompt_cache_options. On GPT-5.6, prompt_cache_options.ttl replaces prompt_cache_retention, which Phaseo does not send to GPT-5.6 models.

Update your request

Start by swapping only the model id and keeping the rest of the request stable. The first examples use the Responses API-style input shape. If you are migrating Chat Completions traffic, keep using messages and the flat reasoning_effort field where the route supports it.
Use max effort only for routes where the extra reasoning budget is worth the latency and cost.
If your integration still sends the flat OpenAI-compatible field, Phaseo also accepts reasoning_effort where the route supports it:

Review pricing

GPT-5.6 pricing is tracked per 1M tokens in the catalog. Cache reads are priced separately from cache writes. In the current catalog, cache reads use a 90% discount from uncached input, while cache writes are priced at 1.25x uncached input. Each input token is billed at one of the three rates. Usage counts cache reads and writes inside input_tokens (prompt_tokens on Chat Completions) and reports writes in cache_write_tokens; see usage and pricing fields.

Use prompt caching deliberately

For repeated context, keep the stable part of the prompt in cacheable blocks and leave request-specific text uncached.
prompt_cache_breakpoint caches everything up to and including its block. A block cache_control such as {"type": "ephemeral"} works too, and Phaseo sends it to GPT-5.6 as prompt_cache_breakpoint. Either mark reaches Claude as a cache breakpoint, so a fallback to Claude still caches. In explicit mode OpenAI caches only the breakpoints you place. The ttl is 30m (the default) or 12h, which OpenAI accepts on its Responses API only; see 12-hour cache on OpenAI. Phaseo does not send prompt_cache_retention to GPT-5.6. See Prompt Caching.

What to test

Reasoning and output quality

  • Sol, Terra, and Luna at the effort levels you expect to expose to users, including max where quality-first workflows justify it
  • standard mode versus reasoning.mode: "pro" on difficult tasks where quality matters more than latency
  • structured outputs and schema pass rate at each effort level
  • tool-call selection and argument quality

Cost and latency

  • latency at each reasoning effort
  • output token growth relative to your current production baseline
  • cache read/write mix on repeated prompts
  • cost per successful task, not just price per token

Rollback

  • keep your previous GPT-5.x route available as a fallback
  • keep max behind a config flag or preset until it is proven on production-like prompts
  • monitor cache write volume separately from cache read volume
  • move GPT-5.6 into default routing only after your own evals confirm task success, cost, and latency

Sources

Last modified on October 21, 2026