On this page · 10 sections
- What OpenAI shuts down on 11 December 2026
- The replacement problem: GPT-5.6 is a generation old and costs more
- Behaviour differences that break migrations
- Decision table: pick a target per workload
- Worked cost examples
- The 30-day migration plan: 11 November to 11 December
- Test plan: what to measure
- Azure, Bedrock and data residency notes
- How eCorpIT can help
- References
Summary. OpenAI stops serving six models in its API on 11 December 2026: gpt-5 (gpt-5-2025-08-07), gpt-5-mini (gpt-5-mini-2025-08-07), gpt-5-nano (gpt-5-nano-2025-08-07), gpt-5-pro (gpt-5-pro-2025-10-06), o3 (o3-2025-04-16) and o3-pro (o3-pro-2025-06-10). Fine-tuned versions go the same day. The notice, dated 11 June 2026, names GPT-5.6 replacements: gpt-5.6-sol for gpt-5 and o3, gpt-5.6-terra for gpt-5-mini, gpt-5.6-luna for gpt-5-nano, and gpt-5.6-sol in pro reasoning mode for both Pro models. Those picks cost more. gpt-5 lists at $1.25 input and $10 output per million tokens; GPT-5.6 Sol is $4 and $20 on a promotion that ends on 30 November 2026, eleven days before the cut-off, and OpenAI has not published the rate after that. gpt-5-mini at $0.25 and $2 maps to Terra at $2 and $12, eight times the input price. The GPT-6 family is often cheaper: GPT-6.1 Sol costs $2 and $10, GPT-6 Luna $0.10 and $0.50. On Vals AI's Terminal-Bench 4.0 run, GPT-6.1 Sol scored 55.05% at $1.72 per task against 37.88% at $7.98 for GPT-5.6 Sol. Test OpenAI's named pick and one GPT-6 model per workload, set reasoning effort on every call, check rate limits, and finish the rollout by 4 December.
About this article. For engineering leads and developers who call OpenAI models directly or through Azure. We checked every date, model ID, price, rate limit and parameter against OpenAI's deprecations page, model pages, pricing page, guides and changelog, Microsoft's Foundry retirement schedule and Vals AI's published leaderboard on 11 November 2026. Prices are US dollar list prices and change often, so re-check before you commit; no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.
What OpenAI shuts down on 11 December 2026
OpenAI's deprecations page lists the notice under 11 June 2026. It says OpenAI told developers using the older GPT-5 and o3 snapshots that day that the models leave the API on 11 December 2026, which meets the minimum six months' notice its policy sets for generally available models. All six model pages now show a Deprecated status. The table draws on those pages and the pricing page.
| Model ID (alias) | Snapshot | Price per 1M tokens (input / cached / output) | Context and max output | OpenAI's named replacement |
|---|---|---|---|---|
| gpt-5 | gpt-5-2025-08-07 | $1.25 / $0.125 / $10 | 400K (272K max input), 128K out | gpt-5.6-sol |
| gpt-5-mini | gpt-5-mini-2025-08-07 | $0.25 / $0.025 / $2 | 400K (272K max input), 128K out | gpt-5.6-terra |
| gpt-5-nano | gpt-5-nano-2025-08-07 | $0.05 / $0.005 / $0.40 | 400K (272K max input), 128K out | gpt-5.6-luna |
| gpt-5-pro | gpt-5-pro-2025-10-06 | $15 / none / $120 | 400K, 272K out | gpt-5.6-sol in pro mode |
| o3 | o3-2025-04-16 | $2 / $0.50 / $8 | 200K, 100K out | gpt-5.6-sol |
| o3-pro | o3-pro-2025-06-10 | $20 / none / $80 | 200K, 100K out | gpt-5.6-sol in pro mode |
Four details matter for planning:
- Alias and snapshot go together. Code that calls
gpt-5resolves togpt-5-2025-08-07, the only snapshot the page lists, so both strings fail on the same day.
- OpenAI's own pages point different ways. The deprecation table names gpt-5.6-sol for gpt-5, but the GPT-5 model page now recommends GPT-6 Astra, which lists at $10 input and $50 output. The gpt-5-mini and gpt-5-nano pages point to GPT-5.6 Terra and Luna, and the o3 page still names GPT-5, which retires the same day, as its successor. Treat the named replacement as a safe default, not the only option.
- You can check dates in code. The List models and Retrieve model endpoints return an optional
shutdown_datefield as aYYYY-MM-DDstring, or null when no date is set. A nightly job that alerts on any model you call with a date set catches the next notice too.
- Dedicated capacity is a sales conversation. OpenAI says some developers may be able to provision dedicated capacity to keep using a model after its shutdown date, through its sales team. Treat that as an exception path for contract-bound workloads, not a plan.
Later removals follow: our guide to the GPT-4o and GPT-4.1 shutdown on 14 January 2027 covers the next large one, and the GPT-5.1 and GPT-5.3-Codex removal on 1 April 2027 the one after.
The replacement problem: GPT-5.6 is a generation old and costs more
OpenAI released the GPT-5.6 family on 9 July 2026. Since then it has released GPT-6 Astra (3 September), GPT-6 Sol and GPT-6 Luna (22 September), GPT-6.1 Sol (29 September) and GPT-6.1 Terra (26 October). Its later notices name GPT-6 targets: gpt-6-luna for GPT-4o and GPT-4.1, gpt-6-sol for GPT-5.1. Three facts change the decision.
First, GPT-5.6 Sol's price is promotional. Its model page lists $4 input, $0.40 cached and $20 output, describes them as 20% below the previous input price and 33% below the previous output price, and says the promotion runs until 30 November 2026. The changelog entry for the cut, dated 21 August 2026, gave an end of at least 21 November; the model and pricing pages now say 30 November. OpenAI has not published the rate from 1 December. Reversing the stated cuts gives $5 and $30 ($4 ÷ 0.8 and $20 ÷ 0.667), so budget for that until OpenAI says otherwise.
Second, the GPT-6 models are cheaper than their GPT-5.6 equivalents. The table compares each retiring model with OpenAI's pick and with the GPT-6 model we would test first, using standard prices per million tokens from OpenAI's pricing page.
| Retiring model | Named replacement, price | Change vs today | GPT-6 alternative, price | Change vs today |
|---|---|---|---|---|
| gpt-5 ($1.25 / $10) | gpt-5.6-sol, $4 / $20 (promo) | 3.2x input, 2x output | gpt-6.1-sol, $2 / $10 | 1.6x input, same output |
| o3 ($2 / $8) | gpt-5.6-sol, $4 / $20 (promo) | 2x input, 2.5x output | gpt-6.1-sol, $2 / $10 | Same input, 1.25x output |
| gpt-5-mini ($0.25 / $2) | gpt-5.6-terra, $2 / $12 | 8x input, 6x output | gpt-6.1-terra, $1 / $5, or gpt-6-luna, $0.10 / $0.50 | 4x / 2.5x, or 0.4x / 0.25x |
| gpt-5-nano ($0.05 / $0.40) | gpt-5.6-luna, $0.20 / $1.20 | 4x input, 3x output | gpt-6-luna, $0.10 / $0.50 | 2x input, 1.25x output |
| gpt-5-pro ($15 / $120) | gpt-5.6-sol pro mode, $4 / $20 | Lower rate, more tokens | gpt-6.1-sol pro mode, $2 / $10 | Lower rate, more tokens |
| o3-pro ($20 / $80) | gpt-5.6-sol pro mode, $4 / $20 | Lower rate, more tokens | gpt-6.1-sol pro mode, $2 / $10 | Lower rate, more tokens |
Cached input also moves. GPT-6.1 Sol reads cache at $0.10, below gpt-5's $0.125 and o3's $0.50. But GPT-5.6 and later models bill cache writes at 1.25 times the input rate for the default 30-minute lifetime, or 2.5 times for a 12-hour lifetime in the Responses API, where gpt-5 and o3 charged nothing extra for writes. GPT-6 Sol, at $2 input, $0.20 cached and $10 output, sits beside 6.1 Sol and still supports none effort.
Third, independent results favour the GPT-6 models. Vals AI's Terminal-Bench 4.0 leaderboard, updated 9 November 2026, runs every model in the same minimal harness that gives the model a single bash tool. It shows GPT-6.1 Sol at 55.05% for $1.72 per task, GPT-6 Sol at 44.44% for $5.79 and GPT-5.6 Sol at 37.88% for $7.98. GPT-6.1 Terra scored 49.49% ($2.16) against 22.73% ($5.60) for GPT-5.6 Terra, and GPT-6 Luna 13.64% ($0.35) against 11.62% ($0.73) for GPT-5.6 Luna. Terminal-Bench measures long agentic terminal work, so it says little about extraction or classification. It does suggest that following the deprecation table to the letter buys an older model at a higher price.
Behaviour differences that break migrations
Changing the model string is the easy part. These differences cause silent cost increases, 400 errors or changed outputs. Sources: the model pages, OpenAI's reasoning, GPT-6 and prompt caching guides.
| Area | Retiring models | GPT-5.6 replacements | GPT-6 alternatives | What to do |
|---|---|---|---|---|
| Reasoning effort values | gpt-5: minimal, low, medium, high; gpt-5-pro: high only | none, low, medium (default), high, xhigh, max | 6.1 Sol: no none; 6 Sol, 6.1 Terra, 6 Luna: none allowed | Map minimal to low (or none where allowed) and compare; set effort on every call |
| Pro models | Separate IDs, Responses API only | Pro reasoning mode on gpt-5.6-sol, billed at standard token rates | Same pro mode on GPT-6 models | Measure the token multiplier per request before budgeting |
| Multi-turn reasoning | Earlier reasoning not rendered into the next turn by default | Earlier reasoning rendered by default; reasoning.context switches it | 6.1 Sol supports all turns; 6 Sol, 6.1 Terra, 6 Luna do not | Expect larger inputs on long conversations; test both settings |
| Context and long prompts | 400K (272K max input); o3 200K | 1,050,000 window, 922K max input | Same window | Prompts over 272K input tokens cost 2x input and 1.5x output for the whole request |
| Prompt caching | No cache-write charge | Writes at 1.25x input (30 minutes) or 2.5x (12 hours) | Same | Replace prompt_cache_retention with prompt_cache_options.ttl; watch hit rates |
| Tools in Chat Completions | Supported on gpt-5, mini, nano and o3 | Supported | 6.1 Sol and 6.1 Terra: tool calls need Responses; 6 Sol and 6 Luna: only at none | Move tool-using code to the Responses API |
| Rate limits (TPM, Build / Launch / Grow) | gpt-5-mini 2M / 10M / 180M; o3 450K / 2M / 30M | 5.6 Terra and 5.6 Sol 1M / 4M / 40M | 6 Luna 2M / 10M / 180M; 6.1 Terra 1M / 4M / 40M | High-volume gpt-5-mini traffic can hit Terra's lower ceiling |
| Knowledge cutoff | 31 May 2024 (mini, nano) to 30 September 2024 (gpt-5) | 16 February 2026 | 20 April to 1 June 2026 | Re-check answers that depend on dates, versions or library APIs |
Three of these deserve a test case each. The rate-limit drop is easy to miss: gpt-5-mini allows 180 million tokens per minute at the Grow tier, while GPT-5.6 Terra and GPT-6.1 Terra allow 40 million. A batch pipeline that ran comfortably on mini can start returning 429 errors on Terra with no code change.
The pro-mode billing changes shape. OpenAI's reasoning guide says pro mode adds up the model work behind the final answer, bills those tokens at the chosen model's standard rates and does more work than standard mode, while the old Pro model IDs keep their own pricing. The per-token rate falls from $15 and $120 (gpt-5-pro) to $4 and $20 or $2 and $10, but the token count rises by an amount OpenAI does not publish.
The tool list and instruction handling change. GPT-5.6 and GPT-6 models add hosted shell, apply_patch, skills, computer use and tool search to the Responses API, so rerun tool-selection tests with the full production tool list. OpenAI's GPT-6 guide says GPT-6 Astra is more likely to stop and ask a clarifying question and can be more sensitive to instructions in skills and files such as AGENTS.md, and asks you to test its prompts on whichever GPT-6 model you choose. It also says to remove temperature, top_p and top_logprobs when effort is not none. An unattended job that pauses for a question is a failed job.
A minimal request change for a gpt-5 workload moving to GPT-6.1 Sol looks like this:
from openai import OpenAI
client = OpenAI()
resp = client.responses.create(
model="gpt-6.1-sol", # was "gpt-5"
reasoning={"effort": "low"}, # 6.1 Sol has no "none" or "minimal"
input=prompt, # drop prompt_cache_retention; 30-minute caching is the default
)
For gpt-5-pro or o3-pro, keep the Responses API and add mode set to pro inside reasoning on the target model.
Decision table: pick a target per workload
| Pick | If your current workload is |
|---|---|
| gpt-6.1-sol | gpt-5 or o3 running coding agents, analysis or multi-step tool use, already on the Responses API, and fine with low as the lowest effort |
| gpt-6-sol | gpt-5 with Chat Completions function calling, where you can run at none effort and cannot move to Responses before 11 December |
| gpt-5.6-sol | Change control requires OpenAI's named replacement, or you need reasoning with tool calls inside Chat Completions; budget at $5 and $30 after 30 November |
| gpt-6.1-sol in pro mode | gpt-5-pro or o3-pro for high-value review or research, with background-friendly latency |
| gpt-6.1-terra | gpt-5-mini for writing, visual reasoning or screen understanding where Luna's quality falls short |
| gpt-6-luna | gpt-5-nano, or gpt-5-mini on classification, extraction, routing and short summaries, at none effort |
| gpt-5.6-terra or gpt-5.6-luna | Only if an auditor or contract insists on the named replacement; both cost more than the GPT-6 options above |
Worked cost examples
These scenarios use list prices and hold token counts constant. Newer models often use different numbers of reasoning tokens for the same job, so replace our volumes with your own measured ones.
Scenario A: gpt-5 support agent. 1,000 million input tokens a month, 60% served from cache (600 million), 400 million uncached, 100 million output tokens. For the newer models we show a range: uncached tokens billed at the input rate (low) or all as 30-minute cache writes (high). Rates come from OpenAI's pricing page.
| Monthly line | gpt-5 today | gpt-5.6-sol at promo ($4 / $20) | gpt-5.6-sol at $5 / $30 | gpt-6.1-sol ($2 / $10) |
|---|---|---|---|---|
| Cached input, 600M | 600 × $0.125 = $75 | 600 × $0.40 = $240 | 600 × $0.50 = $300 | 600 × $0.10 = $60 |
| Uncached input, 400M | 400 × $1.25 = $500 | $1,600 to $2,000 | $2,000 to $2,500 | $800 to $1,000 |
| Output, 100M | 100 × $10 = $1,000 | 100 × $20 = $2,000 | 100 × $30 = $3,000 | 100 × $10 = $1,000 |
| Total | $1,575 | $3,840 to $4,240 | $5,300 to $5,800 | $1,860 to $2,060 |
Following OpenAI's mapping more than doubles this bill even at the promotional price ($3,840 ÷ $1,575 = 2.4x). GPT-6.1 Sol adds 18% to 31%, and its lower token use per task on the Vals agent run (2.86 million against 10.49 million for GPT-5.6 Sol) suggests the real gap may be smaller.
Scenario B: gpt-5-mini extraction pipeline. 3,000 million input and 300 million output tokens a month, no caching.
| Target | Arithmetic | Monthly cost | vs today |
|---|---|---|---|
| gpt-5-mini (today) | 3,000 × $0.25 + 300 × $2 | $1,350 | Baseline |
| gpt-5.6-terra (named) | 3,000 × $2 + 300 × $12 | $9,600 | 7.1x |
| gpt-6.1-terra | 3,000 × $1 + 300 × $5 | $4,500 | 3.3x |
| gpt-6-luna | 3,000 × $0.10 + 300 × $0.50 | $450 | 0.33x |
The named replacement turns a $1,350 line into $9,600. If Luna at none effort passes your extraction tests, the bill falls by two thirds instead.
Scenario C: gpt-5-nano classifier. 5,000 million input and 250 million output tokens. Today: 5,000 × $0.05 + 250 × $0.40 = $350. GPT-5.6 Luna: 5,000 × $0.20 + 250 × $1.20 = $1,300. GPT-6 Luna: 5,000 × $0.10 + 250 × $0.50 = $625. OpenAI prices Batch at 50% of Standard for GPT-6 Luna, so a job that can wait for asynchronous results costs $312.50, just under today's Standard bill (gpt-5-nano on Batch would be $175).
Pro workloads. An o3-pro job using 20 million input and 10 million output tokens a month costs 20 × $20 + 10 × $80 = $1,200. On GPT-6.1 Sol in pro mode, the same token count would cost 20 × $2 + 10 × $10 = $140. Pro mode will not use the same token count, so measure the multiplier on 50 real prompts before you commit to a number.
The 30-day migration plan: 11 November to 11 December
There are 30 days from 11 November to the shutdown. Leave the last week as buffer: the end of the GPT-5.6 Sol promotion on 30 November and the doubling of Gemini 4 Carbon's price on 1 December, from $2 and $10 to $4 and $20, land in the same window and may prompt late re-routing. Our note on the Gemini 4 Carbon price increase has the detail.
| Dates | Work | Exit criterion |
|---|---|---|
| 11 to 15 Nov | Inventory every call to the six model IDs and snapshots in code, config, prompt files, CI, Codex config.toml and gateway routes; cross-check the usage dashboard by project key | Owner and target shortlist per workload |
| 16 to 20 Nov | Build golden sets of 100 to 300 real inputs per workload; record baselines on the retiring model (quality, tokens, latency, cost) | Baseline report signed off |
| 21 to 26 Nov | Run each golden set on two targets, the named GPT-5.6 model and the best GPT-6 candidate, at two effort levels; fix prompts, schemas and tool definitions | One target chosen per workload |
| 27 Nov to 1 Dec | Shadow traffic through the gateway; compare outputs and cost per successful task; recheck the GPT-5.6 Sol price after 30 November | No regression on shadow traffic |
| 2 to 4 Dec | Canary at 5%, 25%, then 100%; keep a feature flag to roll back | Full traffic on new targets |
| 5 to 10 Dec | Remove old model IDs, add a CI check that blocks them, alert on shutdown_date; watch 429s and cache hit rate | No calls to retiring IDs in logs |
| 11 Dec | Shutdown day | Requests to the six models fail |
If you planned to run the golden sets on OpenAI's hosted Evals platform, it became read-only on 31 October and shuts down on 30 November 2026, the same day as Agent Builder and reusable prompt objects; OpenAI points to Promptfoo.
Test plan: what to measure
A migration test should answer one question: does the new model produce acceptable output at an acceptable cost per successful result? Measure these on every golden set.
- Task success. Exact-match or rubric score for extraction and classification; tests passed for code; human-graded samples for open text. Set a regression threshold in advance, for example no more than two points below baseline.
- Schema and tool accuracy. Structured-output validity, correct tool chosen, valid arguments and no unrequested tool calls, run with the full production tool list.
- Tokens per request, split four ways. Uncached input, cached input, cache writes and output including reasoning. OpenAI reports reasoning tokens under
output_tokens_detailsin the usage object.
- Latency. p50 and p95 time to first token and to completion, at the effort level you plan to ship.
- Cost per successful task. Total cost divided by passing outputs. A cheaper model that fails more often can cost more.
- Behaviour checks. Clarifying-question rate in unattended jobs, refusal rate, and answers that depend on dates, since knowledge cutoffs move by up to two years.
- Load. A burst test at peak traffic against the target model's tokens-per-minute limit for your tier.
Keep the golden sets after the move. The GPT-5.1 removal on 1 April 2027 and any future GPT-5.6 notice will need the same tests.
Azure, Bedrock and data residency notes
Azure dates differ, and o3 goes first. Microsoft Foundry's model retirement schedule lists o3 (2025-04-16) and o3-pro (2025-06-10) retiring on 19 November 2026, 22 days before OpenAI's date, with gpt-5.6-sol as the replacement. gpt-5 and gpt-5-nano (2025-08-07) retire on 9 February 2027, gpt-5-pro on 7 April 2027 and gpt-5-mini on 13 July 2027, all with no replacement named. GPT-5.6 Sol, Terra and Luna run on Azure until 11 January 2028. Teams that fail over between OpenAI and Azure need both calendars; our Azure OpenAI GPT-5 retirement checklist covers the Azure side.
Bedrock. OpenAI's model pages list Bedrock IDs such as openai.gpt-5.6-sol and openai.gpt-6.1-sol. OpenAI's deprecations page covers its own API, so confirm Bedrock dates in AWS's documentation rather than assuming OpenAI's.
Data residency. OpenAI adds 10% to regional processing (data residency) endpoints for models released on or after 5 March 2026, which covers every GPT-5.6 and GPT-6 target and none of the retiring models. A team that used gpt-5 through a regional endpoint pays the new rate plus 10%. Fast mode supports EU data residency for GPT-6.1 Sol, GPT-6.1 Terra and GPT-6 Luna but not for GPT-6 Sol. For Indian teams handling personal data, check where inference runs, not only where data is stored.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. For a model migration, our AI evals and observability service builds the golden sets, runs candidate models side by side and reports cost per successful task before you switch. Talk to us at /contact-us/.
Last updated: 11 November 2026.