AIThis post was created with the assistance of artificial intelligence (AI).

By Thorsten Meyer | November 1, 2026 | ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on tech for your team

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

Somewhere in your company there is probably a line like model: "gpt-4o". It sits in a config file, a test fixture or a no-code automation that someone built in 2024 and nobody has touched since. On 14 January 2027, OpenAI switches that model off in its API. Five weeks earlier, on 11 December, GPT-5, GPT-5 mini and GPT-5-nano go. And some older IDs already stopped working on 23 October, which means a few requests may be failing right now.

In the same week, OpenAI rewrote the Model Spec, its public rulebook for how its models should behave. It drops most of the detailed style guidance and tells the model to read instructions for their intent. Two changes, one practical question: what do you have to do before your app starts answering differently, or not at all? This guide sorts out the dates, the price differences, the behavior traps, and a test plan you can run before the deadline.

Key takeaways

  • Three dates matter most. 11 December 2026: gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3 and o3-pro leave the API. 14 January 2027: the remaining GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini snapshots follow. Already gone since 23 October: among others gpt-4.1-nano, the first GPT-4o snapshot, gpt-4-turbo, gpt-3.5-turbo, o1 and o4-mini.
  • Fine-tuned models die with their base. OpenAI says fine-tuned versions follow the base model’s shutdown schedule. The replacements it lists do not support fine-tuning.
  • ChatGPT users already lost GPT-4o in February. OpenAI removed GPT-4o, GPT-4.1 and GPT-4.1 mini from ChatGPT on 13 February 2026. This round is about the API, which means about the apps and bots built on it.
  • Cheaper per token in January, pricier in December. The listed replacement for the GPT-4o family, gpt-6-luna, costs $0.10 per million input tokens against $2.50 for GPT-4o. But gpt-5-nano users move to gpt-5.6-luna at four times the input price, and gpt-5-mini users to gpt-5.6-terra at eight times.
  • The replacements think before they answer. They are reasoning models. Hidden reasoning tokens are billed as output, some sampling parameters must go, and a tight output limit can end in an empty, billed answer.
  • The new Model Spec stops promising a house style. The 29 October version removes most style sections, including the default to format answers in Markdown. If your app depends on a format, say so in the request. OpenAI itself writes that its models “do not yet fully reflect” the Spec.
Video: OpenAI switches off GPT-4o, GPT-4.1 and GPT-5-nano. The shutdown calendar, what the replacements cost, the reasoning catch, the new Model Spec and a test plan, with animated charts, in about five minutes. Narration: AI voice clone of Thorsten Meyer; images AI-generated.

Products Worth Considering

Samsung 32-inch Odyssey OLED G8 (G80SH) 4K QD-OLED Gaming Monitor

Samsung 32-inch Odyssey OLED G8 (G80SH) 4K QD-OLED Gaming Monitor

LG UltraGear 32GX850A-B 32-inch 4K UHD Glossy OLED Gaming Monitor

LG UltraGear 32GX850A-B 32-inch 4K UHD Glossy OLED Gaming Monitor

As an affiliate, we earn on qualifying purchases.

The shutdown calendar

All dates below come from OpenAI’s deprecations page, which I checked on 1 November 2026. OpenAI says it emails affected customers and documents each deprecation there.

  • Already shut down (23 October 2026). Announced in April: gpt-3.5-turbo, gpt-4, gpt-4-turbo, gpt-4.1-nano, the original GPT-4o snapshot gpt-4o-2024-05-13, o1, o1-pro, o3-mini, o4-mini and the image model gpt-image-1. If any of these still sit in your code, those calls fail today.
  • 30 November 2026. Not a model, but it matters for testing: OpenAI shuts down its Evals platform, the Agent Builder and the reusable prompt objects (v1/prompts). Existing evals became read-only on 31 October.
  • 11 December 2026. Notified on 11 June: gpt-5 goes to gpt-5.6-sol, gpt-5-mini to gpt-5.6-terra, gpt-5-nano to gpt-5.6-luna. o3 moves to gpt-5.6-sol; gpt-5-pro and o3-pro to gpt-5.6-sol with its pro reasoning mode.
  • 14 January 2027. Notified on 14 October: gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14 and gpt-4.1-mini-2025-04-14. The recommended replacement for all of them is gpt-6-luna.
  • Later in 2027. Text-to-speech models such as tts-1 on 6 January, older audio and realtime models including the GPT-4o audio variants on 20 January, whisper-1 and the GPT-4o transcription models on 26 February, and gpt-5.1, gpt-5.4-nano and gpt-5.3-codex on 1 April.

Two details are easy to miss. First, the tables list dated snapshots, not the short names most people type. The model pages for the plain gpt-4o, gpt-4o-mini, gpt-4.1 and gpt-4.1-mini names already show the status “Deprecated”, and the snapshots behind them are on the January list. Treat the short names as part of that date. Second, the notice period. The same page promises at least six months’ notice for generally available models, unless safety or compliance concerns require a faster timeline. From 14 October to 14 January is three months. The entry does not say which rule applies. If you have a contract or a committed spend with OpenAI, that is worth a question to your account team. OpenAI also says some customers may be able to buy dedicated capacity for continued access after a shutdown.

Thorsten Meyer AI
API · not ChatGPT

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.

  1. 23 Oct 2026Already off
    Already 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.

  2. 30 Nov 2026Your tests
    Evals platform, Agent Builder, reusable prompts

    Not models, but tools many teams test with. Existing evals became read-only on 31 Oct. Export them first.

  3. 11 Dec 2026Notified 11 Jun
    GPT-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)

  4. 14 Jan 2027Notified 14 Oct
    GPT-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.

  5. Jan to Apr 2027Plan ahead
    Audio, speech, older GPT-5.x

    6 Jan: tts-1 and 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

From 14 October to 14 January is three months. The same page promises at least six months for generally available models, unless safety or compliance require faster.The GPT-4o entry does not say which rule applies.

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

What the replacements cost

The official pricing page lists standard prices per million tokens. The comparison below uses the short-context prices, which apply to prompts up to 272,000 tokens. I checked it on 1 November 2026; prices change, so check again before you budget.

An old wooden card catalogue cabinet with one small drawer pulled open, full of blank index cards
Finding every model ID means looking in more drawers than the code. AI-generated illustration.
  • GPT-4o → GPT-6 Luna: $2.50 input and $10.00 output for GPT-4o, against $0.10 and $0.50. Cached input falls from $1.25 to $0.01.
  • GPT-4o mini → GPT-6 Luna: $0.15 and $0.60, against $0.10 and $0.50.
  • GPT-4.1 → GPT-6 Luna: $2.00 and $8.00, against $0.10 and $0.50.
  • GPT-4.1 mini → GPT-6 Luna: $0.40 and $1.60, against $0.10 and $0.50.
  • GPT-5-nano → GPT-5.6 Luna: $0.05 and $0.40, against $0.20 and $1.20. That is four times the input price and three times the output price.
  • GPT-5 mini → GPT-5.6 Terra: $0.25 and $2.00, against $2.00 and $12.00. Eight times the input price, six times the output price.
  • GPT-5 → GPT-5.6 Sol: $1.25 and $10.00, against $4.00 and $20.00. The page notes that GPT-5.6 Sol’s promotional pricing runs at least through 21 November 2026.

So the January move looks like a discount, and the December move looks like a price increase. Both readings are only half true, because the price per token is not the price per task. GPT-4o and GPT-4.1 answer directly. All the listed replacements are reasoning models, and OpenAI’s reasoning guide says their hidden reasoning tokens “are billed as output tokens”. A model with a lower price per token can still cost more per answer if it thinks a lot. The opposite also happens: in my own newsroom test of a sibling model, GPT-6.1 Terra was cheap per task, and its maximum setting was the worst.

A second point is my own reading of the price list, not an OpenAI recommendation. For the December group, OpenAI lists GPT-5.6 models as replacements, while the newer GPT-6 family is cheaper per token on the same page: gpt-6-luna at $0.10 and $0.50, gpt-6.1-terra at $1.00 and $5.00, gpt-6.1-sol at $2.00 and $10.00. If you migrate anyway, test a GPT-6 option alongside the listed one. Regional processing endpoints add 10% for models released since March 2026. For the wider price fight between the labs, see the AI price war and its fine print.

Thorsten Meyer AI
List prices · 1 Nov 2026

Infographic 02 · Old model → listed replacement

Cheaper in January, pricier in December, per token

Standard API prices per million tokens, input / output, short context (up to 272,000 input tokens). The replacement is the one OpenAI recommends on its deprecations page.

25×lower input price per token: GPT-4o → GPT-6 Luna
8×higher input price per token: GPT-5 mini → GPT-5.6 Terra
4×higher input price per token: GPT-5-nano → GPT-5.6 Luna
6reasoning levels on GPT-6 Luna, from none to max
  • GPT-4o → GPT-6 Luna
    old $2.50 / $10.00new $0.10 / $0.50
    Cheaper per token
  • GPT-4o mini → GPT-6 Luna
    old $0.15 / $0.60new $0.10 / $0.50
    Cheaper per token
  • GPT-4.1 → GPT-6 Luna
    old $2.00 / $8.00new $0.10 / $0.50
    Cheaper per token
  • GPT-4.1 mini → GPT-6 Luna
    old $0.40 / $1.60new $0.10 / $0.50
    Cheaper per token
  • GPT-5-nano → GPT-5.6 Luna
    old $0.05 / $0.40new $0.20 / $1.20
    4× input · 3× output
  • GPT-5 mini → GPT-5.6 Terra
    old $0.25 / $2.00new $2.00 / $12.00
    8× input · 6× output
  • GPT-5 → GPT-5.6 Sol
    old $1.25 / $10.00new $4.00 / $20.00
    3.2× input · 2× output

Why per token is not per task

  • All listed replacements are reasoning models. Their hidden reasoning tokens are billed as output.
  • A tight max_output_tokens can end in an incomplete, billed answer with no visible text.
  • Measure cost per finished task on your own test set, at two or three reasoning levels.

Also on the same price list

  • gpt-6-luna $0.10 / $0.50 · gpt-6.1-terra $1.00 / $5.00 · gpt-6.1-sol $2.00 / $10.00
  • OpenAI lists GPT-5.6 models for the December group. Testing a GPT-6 option too is my suggestion, not OpenAI’s.
  • GPT-5.6 Sol’s promotional pricing runs at least through 21 Nov 2026.

Sources: OpenAI pricing page, OpenAI deprecations page, OpenAI reasoning guide (all checked 1 Nov 2026). Multiples are rounded from the listed prices. Regional processing endpoints add 10% for newer models.
Powered by Thorsten Meyer AI

What changes besides the price

OpenAI’s migration guide for the GPT-6 family lists the technical changes. These are the ones most likely to break an app that was built for GPT-4o.

  • Reasoning effort is a new dial. gpt-6-luna supports the efforts none, low, medium (the default), high, xhigh and max. GPT-4o never reasoned, so the default is not a like-for-like swap. My reading: start with none or low for simple, high-volume tasks, then compare.
  • Some parameters must go. When reasoning effort is not none, the guide says to remove temperature, top_p and top_logprobs. Old code that sets a temperature can fail or need changes.
  • Tool calls depend on the API you use. GPT-6 Luna supports function calling in Chat Completions only with reasoning effort none. For reasoning with tools, OpenAI points to its Responses API.
  • Tight output limits can bite. If the model hits max_output_tokens while it is still reasoning, the response comes back “incomplete”, possibly before any visible text. OpenAI warns that you can pay for input and reasoning tokens without getting an answer, and suggests reserving at least 25,000 tokens for reasoning and output when you start experimenting.
  • No fine-tuning on the replacements. The model pages for gpt-6-luna and the GPT-5.6 models list fine-tuning as “Not supported”. GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini supported it. Separately, OpenAI says active customers can no longer create new fine-tuning jobs from 6 January 2027. A team that relied on a fine-tuned GPT-4o has to rebuild that behavior with prompts, examples or retrieval, and test it.
  • More context, newer knowledge. GPT-6 Luna has a context window of 1,050,000 tokens and a knowledge cutoff of 18 May 2026, against 128,000 tokens and October 2023 for GPT-4o. Prompts above 272,000 input tokens are billed at a higher long-context rate.

The new Model Spec: fewer style rules, more weight on intent

The Model Spec is OpenAI’s public description of how it wants its models to behave. The version dated 29 October 2026 reorganizes it around five values: faithfulness to human intent, minimizing harm, honesty and transparency, human agency, and care. It now calls the model “GPT” instead of “the assistant”. It adds a section called “Consider context carefully” on how memories and earlier conversations should shape what the model infers. And, in OpenAI’s words, it “retires much of the detailed style guidance”. The Spec is published in the public domain under CC0. Unite.AI reported the same points.

I compared the section headings of the new version with the previous one from 18 August 2026. Several style sections no longer appear, among them “Use Markdown with LaTeX extensions”, “Be concise and conversational”, “Be warm”, “Be suitably professional” and “Be thorough but efficient, while respecting length limits”. Some others were renamed or merged, so a heading count says little. The Spec’s overview now says it “intentionally leaves many details of style, personality, and interaction unspecified”, and that user preferences fill those gaps.

An open notebook with blank pages and a blue fountain pen on a light wooden desk, with two blank sticky notes
The new Model Spec leaves most style questions blank. Write down what you need. AI-generated illustration.

What stays matters as much. The rule for machine-read output is still there: “In programmatic settings, GPT should output exactly what the preceding message has asked for, in the exact format specified.” A JSON schema or an instruction like “just the code” signals that setting. The order of authority is still OpenAI’s root rules, then developer instructions, then user instructions; text inside tool output or pasted documents carries no authority by default. And the default to approach questions objectively stays.

The new part is how instructions get read. Under “Respect the letter and spirit of instructions”, the Spec asks the model to use its best understanding of intent, to notice when a source “may also have overlooked an important consequence”, and, when intent is unclear, to give an answer that works across plausible readings or to state its assumptions. For a chat assistant that is often what people want. For a pipeline that parses every character, a model that second-guesses a prompt is a bug.

Two cautions. OpenAI writes that “Our production models do not yet fully reflect the Model Spec.” The document is a training target, not a description of what your API calls do today. And publishing it did not change any model by itself. The practical consequence for builders, in my reading: do not rely on unwritten defaults. If you need Markdown, plain text, three bullets or a fixed tone, put it in the instructions, use a schema where you can, and test it on each new model. On a related note, OpenAI also updated GPT-6 in ChatGPT on 29 October for Free and Go users and logged-out visitors, to give “more concise responses and reduce overly flattering language”. Why style matters so much to readers is the subject of why AI text is so tiring to read.

Thorsten Meyer AI
Model Spec · 29 Oct 2026

Infographic 03 · The rulebook, revised

Fewer style rules, more weight on intent

OpenAI reorganized its Model Spec around five values and retired most detailed style guidance. Here is what that means for apps that never spelled out their format.

No longer a section

Headings in the 18 Aug 2026 version that do not appear on 29 Oct 2026 (selection)

  • Use Markdown with LaTeX extensions
  • Be concise and conversational
  • Be warm
  • Be suitably professional
  • Be thorough but efficient, while respecting length limits

Still there

Rules that matter for apps and pipelines

  • Programmatic output: exactly what was asked for, in the exact format specified
  • Chain of command: root rules, then developer, then user
  • Tool output and pasted data carry no authority by default
  • Approach questions objectively
  • New: consider context carefully, with user control over memory
“Our production models do not yet fully reflect the Model Spec.”Model Spec, overview, 29 Oct 2026. A training target, not a description of today’s API behavior.

What to do with your prompts

  1. List every prompt that never states a format but expects one: Markdown, plain text, length, tone.
  2. Write the expectation into the developer instructions, or use a JSON schema.
  3. Re-run those prompts on each new model before you switch traffic.

Sources: Model Spec, 29 Oct 2026, Model Spec, 18 Aug 2026, OpenAI blog, 29 Oct 2026. Heading comparison by Thorsten Meyer AI; some sections were renamed or merged rather than removed.
Powered by Thorsten Meyer AI

How to find every model ID

Start with the code, then look where code search cannot see. A plain text search across all repositories catches most hard-coded IDs, including .env, YAML and JSON files. Here is a short, generic starting point:

Search a repository for retiring model IDs
grep -rnE --exclude-dir={.git,node_modules,dist,build} \
  'gpt-4o|gpt-4\.1|gpt-5-(nano|mini|pro)|"gpt-5"|\bo3(-pro)?\b|\bo1\b|o4-mini' .
Generic example, self-written. Run it from the root of a repository.

It works with the grep on macOS and Linux. Read every match before you change anything: short names such as o1 and o3 also match things that are not models, and the plain gpt-5 is only caught in quotes, so that the newer gpt-5.6 names do not flood the results. Then check the places a search misses:

  • IDs built at runtime, for example a version number glued onto “gpt-“. Search for the fragment too.
  • Databases, feature flags and admin settings that store a model name per customer or per workflow.
  • Libraries and tools with their own defaults, such as an SDK wrapper, an agent framework or a plugin that picks a model for you.
  • Everything outside the main repo: infrastructure code, notebooks, spreadsheets with scripts, and no-code automations.
  • The API itself. OpenAI’s list-models endpoint (GET /v1/models) returns an optional shutdown_date for each model. A small scheduled check that compares your configured models with that field turns a surprise into a ticket.

A migration plan you can run before the deadline

  1. Fix what is already broken. Anything that still calls a model from the 23 October list is failing now.
  2. Move the model name into one place. One setting per use case, not forty copies in forty files. It makes the switch, and a rollback, a one-line change.
  3. Build a small golden set from real traffic. Fifty to a few hundred representative requests per use case, with sensitive data removed, plus the answers you consider good. If your tests live in OpenAI’s Evals platform, export them before it shuts down on 30 November. OpenAI’s own cookbook describes a move to the evaluation tool Promptfoo.
  4. Run old and new side by side while you still can. Until 14 January, GPT-4o still answers. Compare format compliance (does the JSON parse, are the headings where your front end expects them), tool calls, refusals, answer length, latency and cost per task, not per token.
  5. Test the prompts that leaned on old style. Look for prompts that never stated a format because the old model “just did it”: Markdown answers, a friendly tone, short replies. Write those expectations into the instructions and test again.
  6. Choose the reasoning effort deliberately. Try two or three levels on the golden set and pick the cheapest one that passes. Set max_output_tokens with room for reasoning.
  7. Roll out in steps. Send a small share of traffic to the new model, watch errors and cost, then widen it. Keep the rollback ready.
  8. Stop the old IDs from coming back. Add the search pattern to your CI pipeline so a copy-pasted example does not reintroduce a retired model.

What this means for companies

The direct cost is an engineering sprint, not a strategy change. The indirect costs hide in three places. Fine-tuned models: whoever paid to train GPT-4o for their tone or their forms loses that work in January and cannot fine-tune the listed replacement. Budgets: teams on gpt-5-mini or gpt-5-nano face higher prices per token in December unless they test cheaper options, while teams on GPT-4o may save money, as long as reasoning stays modest. And testing: the evals platform many teams used for exactly this kind of comparison closes first. The broader lesson is about dependency. A hosted model is a product with an end date. Companies that keep their model names in one place, own their test sets and watch the deprecations feed treat a retirement like a library update. Everyone else finds out from an error log.

What this means for users

If you use ChatGPT directly, this round changes little: GPT-4o and GPT-4.1 already left ChatGPT in February, and today’s models there are newer. What you may notice is in other products. Customer-service bots, writing tools and apps that ran on GPT-4o behind the scenes will switch models around the deadlines. Answers may become shorter or longer, more careful or more direct, and some features may pause while a provider migrates. If a tool you depend on suddenly behaves differently in December or January, that is a likely reason; ask the provider which model it now uses. The new Model Spec also says style should follow your preferences, so it is worth stating them plainly: “answer in three sentences”, “no bullet points”, “be blunt”. For what you get on the paid ChatGPT plans right now, see what ChatGPT Pro’s doubled limits actually give you.

Limits of this guide

  • Dates and prices come from OpenAI’s pages as of 1 November 2026. OpenAI can change them, and the pricing page notes promotional terms. I did not see the emails OpenAI says it sent to affected customers.
  • The trigger was a developer blog post. A post on DEV Community on 31 October flagged the retirements and suggested a search pattern. I used it as a tip and checked every date against OpenAI’s deprecations page; the search pattern above is my own, simpler version.
  • I did not measure behavior. I did not run GPT-4o against GPT-6 Luna for this article. Whether the replacement is better, worse or just different for your task depends on your prompts, which is why the plan above starts with a test set.
  • The Model Spec describes a goal. OpenAI says its models do not yet fully follow it. The heading comparison is my own, between the HTML versions of 18 August and 29 October 2026.
  • The notice-period question is open. The page promises six months for generally available models with exceptions, and gives three months for the GPT-4o family without saying why. I asked no one at OpenAI for this article; the gap is stated, not explained.

Sources

Researched and drafted with AI assistance, including Anthropic’s Claude.

You May Also Like

This Week in Security: Firewall Fixes, a Rented Banking Trojan, a Blank PDF and Stolen Tokens. What to Actually Do

Six of this week’s thirty security stories, checked against the original advisories, each with one clear action: Fortinet’s critical firewall fixes and the still-active FortiBleed campaign, a rented Android banking trojan, a blank PDF invoice that opens a backdoor, a Microsoft Authenticator token flaw, 32 fake AI bots hunting for secrets, and why CISA’s must-patch list is a floor. Patch order for companies, a checklist for users.

60,000 Buyout Offers and a $95 Billion Stock Sale: How Big Tech Now Pays for AI

Microsoft offers voluntary buyouts to about 60,000 employees; the same day Meta launches a plan to raise up to $95 billion in new stock. What the terms and SEC filings actually say, why the AI build-out now lands on employees and shareholders, where AI is the real reason, and what it means for companies and users.

Growth Without Jobs? The US Makes 10% More With Almost the Same Hours. What the Data Says About AI, and What It Doesn’t

US output is up 10% since the end of 2022 while hours worked rose less than 1%. Productivity is beating the last decade, the labor share is the lowest since 1947, and hiring for newcomers has stalled. The FT asks if this is the first clear evidence of AI in the labor market. What BLS, BEA, Census, Fed and Eurostat data really show, why the answer is not yet clear, and what it means for companies and workers.

Mid-Market AI Adoption via Fixed-Scope Pilots: The 6-Week Blueprint

AIThis post was created with the assistance of artificial intelligence (AI).Thorsten Meyer…