🔍 Read the full analysis: Is Your App Ready For GPT-4o, GPT-4.1, And GPT-5-nano To Leave The API? on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
OpenAI’s published API deprecation schedule lists GPT-5, GPT-5 mini, GPT-5-nano and several other models for shutdown on December 11, 2026, followed by GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini snapshots on January 14, 2027. The announced replacements can differ in price and behavior, and older model IDs listed as shut down on October 23 may already fail. Teams should verify their model IDs and test replacement outputs before migration.
OpenAI’s API deprecation schedule lists GPT-5, GPT-5 mini and GPT-5-nano for shutdown on December 11, 2026, and GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini snapshots for January 14, 2027. The changes affect applications and services calling those API model IDs; OpenAI lists replacement models, but developers may need to update configurations and retest behavior, pricing and output formats before the deadlines.
The schedule, as reported by Thorsten Meyer on November 1 and attributed to OpenAI’s deprecations page, includes gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3 and o3-pro on December 11. The listed replacements are from OpenAI’s GPT-5.6 family: for example, gpt-5-nano maps to gpt-5.6-luna, while gpt-5-mini maps to gpt-5.6-terra. GPT-5 and o3 are listed with gpt-5.6-sol; the pro models are listed with its pro reasoning mode.
On January 14, 2027, the listed GPT-4 family snapshots include two GPT-4o versions, GPT-4o mini, GPT-4.1 and GPT-4.1 mini. The source says OpenAI recommends gpt-6-luna for those entries. It also reports that several other IDs, including gpt-4.1-nano, gpt-4-turbo, gpt-3.5-turbo, o1 and o4-mini, were listed as shut down on October 23. If a production request still uses one of those IDs, the source warns it may fail.
The listed API prices vary by model and token type. For example, the source’s short-context comparison gives GPT-4o’s input and output rates as $2.50 and $10 per million tokens, versus $0.10 and $0.50 for gpt-6-luna. By contrast, it says GPT-5-nano users moving to gpt-5.6-luna would see input pricing rise from $0.05 to $0.20 and output pricing from $0.40 to $1.20 per million tokens. These are figures reported from a pricing page checked November 1, 2026, not guaranteed future rates.
Infographic 01 · The shutdown calendar
What stops working, and when
OpenAI's API deprecations, as listed on 1 November 2026. GPT-4o and GPT-4.1 already left ChatGPT on 13 February 2026; this round is about apps built on the API.
- 23 Oct 2026Already offAlready shut down
gpt-3.5-turbo,gpt-4,gpt-4-turbo,gpt-4.1-nano,gpt-4o-2024-05-13,o1,o1-pro,o3-mini,o4-mini,gpt-image-1. Calls to these fail today. - 30 Nov 2026Your testsEvals platform, Agent Builder, reusable prompts
Not models, but tools many teams test with. Existing evals became read-only on 31 Oct. Export them first.
- 11 Dec 2026Notified 11 JunGPT-5 family and o3
gpt-5→gpt-5.6-sol·gpt-5-mini→gpt-5.6-terra·gpt-5-nano→gpt-5.6-luna·o3→gpt-5.6-sol·gpt-5-pro,o3-pro→gpt-5.6-sol(pro mode) - 14 Jan 2027Notified 14 OctGPT-4o, GPT-4o mini, GPT-4.1, GPT-4.1 mini
Snapshots
gpt-4o-2024-08-06,gpt-4o-2024-11-20,gpt-4o-mini-2024-07-18,gpt-4.1-2025-04-14,gpt-4.1-mini-2025-04-14→gpt-6-luna. Fine-tuned versions follow their base model. - Jan to Apr 2027Plan aheadAudio, speech, older GPT-5.x
6 Jan:
tts-1and others · 20 Jan: older audio and realtime models · 26 Feb:whisper-1, GPT-4o transcription · 1 Apr:gpt-5.1,gpt-5.4-nano,gpt-5.3-codex
Sources: OpenAI deprecations page (checked 1 Nov 2026) · OpenAI Help Center, model release notes. Dates as listed by OpenAI; shutdowns can be rescheduled.
Powered by Thorsten Meyer AI
Migration Risks for Live Apps
A model shutdown can turn a configuration detail into an outage: an app that continues calling a retired ID may stop receiving the expected response. The impact depends on where that ID is used, including application code, test fixtures, workflow tools and no-code automations. A search limited to the main codebase may miss integrations maintained by other teams.
Changing the model is not necessarily a drop-in replacement. The source describes the announced alternatives as reasoning models, which may use hidden reasoning tokens billed as output. It also says some sampling parameters may need to be removed and that a restrictive output-token limit can leave an answer empty while still incurring charges. These are operational and billing risks to check against the applicable model documentation and the app’s real workloads.
The potential price effect is uneven. Some GPT-4 family migrations have lower listed per-token rates, while the cited GPT-5-nano and GPT-5-mini replacements cost more per token in the source’s comparison. Actual spend also depends on input and output volume, caching, prompt size and usage patterns. Teams should calculate against their own traffic rather than infer total savings or increases from per-token rates alone.
Popular right now

Ninja DualZone Smart XL Air Fryer, 10-Qt, 6-in-1, DZ950

Bose QuietComfort True Wireless Noise-Cancelling Earbuds, Black

Vitamix Propel Series 510 Professional-Grade Blender, 3 Programs, Black
As an affiliate, we earn on qualifying purchases.
How the Shutdown Schedule Is Set
The dates and mappings in this report come from the schedule described by Thorsten Meyer, who says he checked OpenAI’s deprecations page on November 1, 2026. The article says OpenAI documents deprecations there and emails affected customers. It also reports that fine-tuned models follow their base model’s shutdown schedule, while the listed replacements do not support fine-tuning. Organizations using custom fine-tunes should confirm their own migration options with OpenAI.
The API schedule is distinct from the ChatGPT product change. According to the source, OpenAI removed GPT-4o, GPT-4.1 and GPT-4.1 mini from ChatGPT on February 13, 2026; the current dates concern API access for applications built on OpenAI’s services. The source also notes a separate November 30 shutdown for OpenAI’s Evals platform, Agent Builder and reusable prompt objects, with existing evals becoming read-only on October 31. That may affect teams using those tools to test or manage migrations.
The source says OpenAI’s October 29 Model Spec revision removed much of its detailed style guidance, including a default expectation of Markdown formatting. It reports that the revised document asks models to interpret instructions by intent and that OpenAI says its models “do not yet fully reflect” the Spec. This is relevant to migration testing, but it does not by itself establish how any particular replacement will behave in a given application.
Open Questions on Dates and Behavior
The schedule and prices here are reported from pages checked on November 1, 2026; they can change, and the source does not reproduce the full official notices. It is also unclear from the supplied material whether every customer, region or API configuration has the same migration options. Developers should verify each ID and replacement in OpenAI’s current documentation and account notices.
The source says OpenAI’s page promises at least six months’ notice for generally available models unless safety or compliance concerns require a faster timeline. It notes that the reported notice period for the January 14 shutdown runs from October 14, a shorter interval, but says the entry does not explain which policy applies. OpenAI’s reason for the timing is not established by the material provided.
Replacement behavior, latency, output quality and total cost are also not settled by the listed mappings or token prices. The source warns about reasoning-token billing, parameter changes and output limits, but does not provide independent test results across workloads. Whether a specific application will need prompt changes, different limits or a larger budget depends on its implementation and usage.
Audit IDs and Test Replacements
Teams can start by searching application repositories, deployment settings, test data, workflow platforms and vendor integrations for every affected model ID, including dated snapshots and shorter aliases. Mark IDs already listed as shut down separately from those scheduled for December or January, then identify an owner and fallback plan for each live integration.
Before changing production traffic, run representative prompts against the listed replacement using the application’s real system instructions, tools, structured-output requirements and token limits. Compare response validity, formatting, refusal behavior, latency and usage charges; test empty or truncated outputs as well as normal responses. Review API parameters against the replacement’s documentation, and check whether fine-tuning or evaluation workflows depend on services also scheduled for closure.
Recheck OpenAI’s deprecation notices, model documentation and pricing shortly before each migration. The source says some customers may be able to buy dedicated capacity for continued access after a shutdown, but does not give eligibility or terms; organizations that depend on that option will need to ask OpenAI. The next listed milestones are the November 30 tooling shutdown, December 11 model retirements and January 14 GPT-4 family retirements.
Key Questions
When are GPT-5-nano and GPT-4o scheduled to leave the API?
According to the schedule reported by Thorsten Meyer, GPT-5-nano is listed for December 11, 2026. GPT-4o snapshots are listed for January 14, 2027.
Which replacements does OpenAI list?
The source reports gpt-5.6-luna for GPT-5-nano, gpt-5.6-terra for GPT-5 mini, and gpt-6-luna for the affected GPT-4o and GPT-4.1 family snapshots. Check OpenAI’s current documentation for the mapping that applies to your exact model ID.
Will replacing a model reduce API costs?
Not necessarily. The reported prices show lower per-token rates for some GPT-4 family replacements, but higher rates for the cited GPT-5-nano and GPT-5-mini migrations. Total cost depends on token use and other factors, and the prices may change.
What should developers test before switching?
Test real prompts and application flows, including formatting, structured outputs, tool use, response limits, empty or truncated answers, latency and billed token usage. Also verify whether the replacement supports required parameters or fine-tuning.
Are the dates confirmed for every customer?
The dates are presented in the source as entries on OpenAI’s deprecation schedule, but the supplied material does not establish whether all customers or configurations have identical arrangements. Check OpenAI’s notices and account communications for your specific deployment.
Source: ThorstenMeyerAI.com
