← Startup Signals
9 min readUpdated 2026-10-19Issue 7

OpenAI removes o1, o3-mini, o4-mini and GPT-4 Turbo on 23 October. The replacements it names run from 5.5 times the price to 97 percent less.

Eleven models and six fine tuned models go dark in four days. Here is OpenAI's own mapping, what each landing costs on a typical month of traffic, and the places where the named replacement is not the cheapest or cannot be used at all.

ByKarthik KumarCafiyn Innovations
At a glance
Shutdown date
Friday 23 October 2026, announced 22 April 2026
Models removed
o1, o1 pro, o3-mini, o4-mini, GPT-4, GPT-4 Turbo, gpt-4-1106-preview, GPT-3.5 Turbo 0125, GPT-4.1 nano, gpt-4o-2024-05-13, gpt-image-1
Fine tuned models removed
ft-gpt-3.5-turbo, ft-gpt-4, ft-gpt-4.1-nano, ft-babbage-002, ft-davinci-002, ft-o4-mini
Named replacements
GPT-5.6 Sol, Terra and Luna, and gpt-image-2.5-sunburst or gpt-image-2.5-flare
Fine tuning on the replacements
Not supported on Sol, Terra, Luna or gpt-6-luna
Sol price
$4 input and $20 output per million tokens, promotional through at least 21 November 2026
Check from code
GET /v1/models, optional shutdown_date field
Prices read
OpenAI model pages and deprecations page, 19 October 2026

What stops working on Friday

OpenAI's deprecations page lists a shutdown on 23 October 2026 for eleven models and six fine tuned models. It was announced on 22 April, which is six months, the minimum notice OpenAI's own policy sets for generally available models. The page says that at the shutdown date the model "will no longer be accessible", and it names a replacement for each one.

To compare the landings we priced one reference month: 10 million input tokens and 2 million output tokens, no caching, standard processing, using the list prices on OpenAI's own model pages on 19 October. Your mix will differ, so read the multipliers as direction and not as a quote.

  • o3-mini to gpt-5.6-sol: $19.80 to $80.00 a month, 4.0 times as much.
  • o4-mini to gpt-5.6-terra: $19.80 to $44.00, 2.2 times as much.
  • o1 to gpt-5.6-sol: $270.00 to $80.00, 70 percent less.
  • o1 pro to gpt-5.6-sol with reasoning.mode set to pro: $2,700.00 to $80.00, 97 percent less, before the extra tokens pro mode uses.
  • gpt-4 (gpt-4-0613) to gpt-5.6-sol: $420.00 to $80.00, 81 percent less.
  • gpt-4-turbo to gpt-5.6-sol: $160.00 to $80.00, 50 percent less.
  • gpt-3.5-turbo-0125 to gpt-5.6-terra: $8.00 to $44.00, 5.5 times as much.
  • gpt-4.1-nano to gpt-5.6-luna: $1.80 to $4.40, 2.4 times as much.
  • gpt-4-1106-preview and gpt-4o-2024-05-13 to gpt-5.6-sol: the model pages show no price for these snapshots, so there is no comparison here.
  • gpt-image-1 to gpt-image-2.5-sunburst or gpt-image-2.5-flare: priced per image token, covered below.
  • The six fine tuned models: covered in the fine tuning section below.

Three replacements, three price tiers

GPT-5.6 Sol costs $4 input and $20 output per million tokens, Terra $2 and $12, and Luna $0.20 and $1.20. OpenAI describes Terra as roughly the mini tier of earlier GPT-5 families and Luna as the nano tier. Each lists a maximum of 922,000 input tokens, and each prices a prompt over 272K input tokens at 2x input and 1.5x output for the whole request. Cached input is a tenth of the input rate, and cache writes bill at 1.25 times the uncached input rate.

If you are coming from o3-mini or o1, whose context window is 200,000 tokens, the 272K rule matters only once you start sending longer prompts. It is worth knowing before you do, because it reprices the whole request and not just the part over the line.

Two places the named replacement is not the cheapest landing

GPT-3.5 Turbo is the clearest case. OpenAI names Terra, which on the reference month costs 5.5 times as much as gpt-3.5-turbo ($44.00 against $8.00). GPT-5.6 Luna would cost $4.40, 0.55 times as much, and gpt-6-luna $2.00, 0.25 times as much. Both are priced on the same OpenAI pages.

GPT-4.1 nano is the second. The named landing, GPT-5.6 Luna, is 2.4 times the price ($1.80 to $4.40), while gpt-6-luna costs $2.00, 1.1 times. OpenAI itself names gpt-6-luna as the replacement for GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini in its 14 October notice, which removes those on 14 January 2027, so it is not an exotic choice.

Price is one axis. A cheaper model that fails your evals is not cheaper, and we have no data on how your workload behaves on any of these. The point is narrower: the mapping table is OpenAI's default and not a cost optimisation, so test the cheaper landing before you accept the named one.

Sol is a promotional price

The Sol model page says its price is a promotion: "GPT-5.6 Sol's promotional pricing is available at least through November 21, 2026." It describes $4 and $20 as a 20% cut in input price and a 33% cut in output price, which implies earlier prices of about $5 and $30.

That matters because Sol is the landing for most of the removed models. On the reference month Sol costs $80.00 at $4 and $20, and about $110.00 at $5 and $30. At the higher price the saving against o1 is 59 percent, against o1 pro 96 percent, against GPT-4 74 percent and against GPT-4 Turbo 31 percent. For o3-mini the cost multiple rises from 4.0 to 5.6. The page promises the lower price only through 21 November, so a budget that assumes $4 and $20 for good is a bet.

Reasoning tokens decide the real bill

Sol, Terra and Luna are reasoning models, and so are o1, o3-mini and o4-mini. OpenAI's reasoning guide says reasoning tokens are not visible through the API, occupy space in the context window, and are billed as output tokens. Output is the expensive side of every price above, so the same prompt can cost more or less on a new model depending on how much it thinks.

The guide says GPT-5.6 defaults to a reasoning.effort of medium, and the Terra and Luna pages list none, low, medium, high, xhigh and max. For a workload you are moving off a cheap model, test the lowest effort that passes your evals before you test the default, and compare total output tokens per request and not only the price per token.

Fine tuned models have nowhere to go

The table lists six fine tuned models for removal on 23 October: ft-gpt-3.5-turbo, ft-gpt-4, ft-gpt-4.1-nano, ft-babbage-002, ft-davinci-002 and ft-o4-mini. For each it names a recommended replacement base model: Terra, Sol, Luna, Terra, Terra and Terra.

OpenAI's model pages list fine tuning as not supported on gpt-5.6-sol, gpt-5.6-terra, gpt-5.6-luna and gpt-6-luna. So the replacement base model cannot be fine tuned, and whatever behaviour you trained in has to be rebuilt another way: a longer prompt, examples in context, retrieval, or a different provider. Start with the prompt, since that is the part you can test this week.

The self serve fine tuning notice on the same page narrows the runway further. Organisations that had not run inference on a fine tuned model in the past 60 days could no longer create jobs from 2 July, and active customers lose the ability to create new jobs on 6 January 2027. Inference on a fine tuned model stops when its base model is deprecated.

Images: cheaper per token, unknown per image

gpt-image-1 is replaced by gpt-image-2.5-sunburst or gpt-image-2.5-flare. On image tokens gpt-image-1 lists $10 input, $2.50 cached input and $40 output per million tokens, and gpt-image-2.5 lists $8, $2 and $30, which is 20 percent less on input and 25 percent less on output. Text input is $5 on both.

The 2.5 page also says its token rates match GPT Image 2 and that the GPT Image 2 calculator does not estimate GPT Image 2.5 token consumption, so the cost of an image cannot be read off the rate card. Generate a representative batch and read the usage before you commit. The next image removals follow on 1 December, for gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest.

Find every call before Friday

OpenAI documents an optional shutdown_date field on the List models endpoint, a YYYY-MM-DD string or null when none is announced, also returned by Retrieve a model. One request shows every model your key can see that has a date. That lists what is available to the key and not what your code calls, so it complements a code search and does not replace it.

Escalation paths hide most often. Teams route to a reasoning model for the hard case, the retry after a cheaper model failed validation. That branch is the least exercised in testing and the first to break on Friday.

  • curl -s https://api.openai.com/v1/models -H "Authorization: Bearer $OPENAI_API_KEY" | jq -r '.data[] | select(.shutdown_date != null) | "\(.shutdown_date) \(.id)"' | sort
  • grep -rnE "\bo1\b|o1-pro|o3-mini|o4-mini|gpt-4-turbo|gpt-4-0613|gpt-4-1106|gpt-3\.5-turbo|gpt-4\.1-nano|gpt-4o-2024-05-13|gpt-image-1|ft:" .
  • The pattern also matches gpt-image-1-mini, which is removed on 1 December, so read each hit.
  • Check environment variables, feature flags and any model name stored per customer in your database.
  • Check scheduled jobs, webhooks and admin only features, which fail into a log and not into a user's face.

What comes after Friday

This is the first of several dated removals: older GPT-5 and o3 snapshots on 11 December, GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini on 14 January 2027, and gpt-5.3-codex, gpt-5.1 and gpt-5.4-nano on 1 April 2027. We keep every dated deadline from OpenAI, Anthropic, Google and GitHub on one page, with a calendar feed you can subscribe to.

What to do

  1. 1Run the List models request and the code search above today, and write down every hit with its owner.
  2. 2Decide each replacement on measured quality and cost: test the named one, and also the cheaper landing where one exists, Luna or gpt-6-luna for gpt-3.5-turbo and gpt-4.1-nano.
  3. 3Rerun your evals on the replacement with reasoning.effort set deliberately, and compare total output tokens per request.
  4. 4If you use a fine tuned model, plan its replacement as a prompt, retrieval or provider change, because none of the named base models supports fine tuning.
  5. 5Cost o1, GPT-4 and o3-mini migrations on Sol at $4 and $20 and again at about $5 and $30, and put 21 November in your calendar.
  6. 6Switch gpt-image-1 calls to gpt-image-2.5-sunburst or gpt-image-2.5-flare, and read token usage on a sample batch before you commit.
  7. 7Subscribe to the deadlines calendar so the next removal reaches you a week early.

Common questions

When does OpenAI shut down o3-mini?

On 23 October 2026. OpenAI announced it on 22 April 2026, together with o1, o1 pro, o4-mini, GPT-4, GPT-4 Turbo, GPT-3.5 Turbo 0125, GPT-4.1 nano, gpt-4o-2024-05-13 and gpt-image-1.

What replaces o3-mini?

OpenAI names gpt-5.6-sol. On a month of 10 million input and 2 million output tokens it costs $80.00 against $19.80 for o3-mini, about 4.0 times as much, at Sol's promotional price of $4 and $20. Terra, at $44.00, is 2.2 times as much and is worth testing first.

What replaces o4-mini?

gpt-5.6-terra, at $2 input and $12 output per million tokens against $1.10 and $4.40 for o4-mini, which is 2.2 times as much on a typical mix.

What replaces GPT-4 Turbo?

gpt-5.6-sol, at $4 and $20 against $10 and $30. On the reference month that is $80.00 against $160.00, half the cost, at the promotional price.

What replaces gpt-3.5-turbo-0125?

OpenAI names gpt-5.6-terra, which costs 5.5 times as much on the reference month ($44.00 against $8.00). GPT-5.6 Luna ($4.40) and gpt-6-luna ($2.00) cost less than gpt-3.5-turbo does and are worth testing.

What replaces GPT-4.1 nano?

OpenAI names gpt-5.6-luna in the 23 October entry, at $0.20 and $1.20 against $0.10 and $0.40. gpt-6-luna, at $0.10 and $0.50, is the model OpenAI names for the GPT-4.1 and GPT-4o families in its 14 October notice.

What happens to my fine tuned models?

They are removed on 23 October, and OpenAI names a replacement base model for each. The model pages list fine tuning as not supported on Sol, Terra, Luna and gpt-6-luna, so those base models cannot be fine tuned to recreate them.

Does gpt-image-1 stop working too?

Yes, on 23 October. OpenAI names gpt-image-2.5-sunburst or gpt-image-2.5-flare. Image token rates are lower on 2.5, but OpenAI says its calculator does not estimate 2.5 token use, so measure real usage.

How can I check my models for shutdown dates from code?

Call the List models endpoint and read the optional shutdown_date field, a YYYY-MM-DD string or null. It is also on the Retrieve a model endpoint. It lists what your key can see, so search your code as well.

Will OpenAI move my requests to the new model automatically?

The deprecations page says the model will no longer be accessible at the shutdown date and names a recommended replacement. It describes no automatic routing, so plan to change the model string yourself.

Sources

Read against the primary documentation rather than secondary coverage. Where a figure comes from a provider's own docs, it is quoted as published on 2026-10-19.

Related

More from Signals

OpenCode says a breach hit 1.4 percent of Console users who linked an AI provider. Rotate those keys before the root cause is published.
OpenCode has confirmed the breach and has not said how it happened or what was taken. Here is what the vendor said, who is exposed, the order to work in, and how to limit the damage next time.
GitHub Actions workflow lockfiles are in public preview. Here is how to turn them on, check them in CI, and what they do not protect.
A tag can move after you reviewed it. A lockfile makes the runner use the commit you reviewed. Here is the setup, the CI check, the policy, and what a lockfile cannot tell you.
Next.js 16.4.1 and 15.5.28 fix two critical remote code execution flaws. For one of them there is no workaround.
Two of the three fixes were postponed from September. Here is what each flaw needs in order to be reachable, the one workaround that exists, and what the announcement leaves out.
A poisoned npm release that punishes you for revoking the stolen token. The order of your response is the whole defence.
Most incident guidance starts with revoking the leaked token. Here that is the trigger. What StepSecurity found, the order it recommends, and why a valid provenance attestation did not help.
Claude Haiku 5.5 costs a tenth of Haiku 4.5 per token. One token past 100,000 it costs half.
The rate card is a tenth of Haiku 4.5. The footnote is a threshold that moves the price fivefold and that a tokenizer change pushes you toward.
Gemini 4 Argon launched at $2 and $10 and goes to $4 and $20 on 1 December. Price your product on the second number.
Every tier on the pricing page doubles on the same date. What changes, what the number includes, and what to do if you are building on the launch rate.
Claude Haiku 5.5 is not a model id swap. Five things that worked on Haiku 4.5 now return a 400.
The model id is the easy part. The requests that now fail, the response parsing that changes, and the details that fail quietly.
Next.js shipped 16.3.7 and 16.3.8 a day apart. Only one of them is the security release.
Two patch releases a day apart, one of them a decoy if you are not reading carefully. And the 15.5 line does not get the high severity fix at all.
The EU AI output marking rule is not a December deadline. For most teams it started in August.
Almost every summary of this gives one date. There are two, and which one applies to you depends on when you shipped, not on how big you are.
Sonnet 5.5 cut the rate by a third and the token count went up by about 30 percent.
A third off the per-token rate is not a third off the bill when the same text now costs more tokens. Here is the arithmetic, and the five ways your code can break.
Your AI gateway holds every provider key you have. A 9.9 just landed in LiteLLM.
An AI gateway concentrates every upstream key into one process. That is the point of it, and it is why a privilege escalation there is worse than it looks.
The table your coding agent created does not have row level security on it.
Dashboard-created tables get row level security by default now. API-created tables do not, and API is how your coding agent works.
A 9.5 in next/og. Whether it reaches you depends on one line in your OG route.
The advisory rates it 9.5, but it only fires if your OG image route puts attacker-controlled text into SVG. Here is how to find out which side of that line you are on.
OpenAI and Anthropic both cut prices on 22 September. One of them costs you a refactor.
Two frontier price cuts in one day is a good week for anyone paying a token bill. The migration cost is not evenly distributed, and one of the two prices comes with an expiry hedge.
A package install reads your home directory. This week two of them did it on purpose.
The implant did nothing clever. It read the files your shell reads, in the place your credentials live, and sent them somewhere else. That is the whole attack, and it works.
GitHub is switching off SHA-1 SSH keys. Find out now whether yours is one of them.
The keys at risk are the old ones, on the machines nobody logs into, in the pipelines that have run untouched for three years. Those are also the ones that will fail loudest.
Every third-party script tag is a standing grant to run code on your visitors.
A marketing form, a chat widget, an analytics snippet. Each one is permission for someone else's server to execute whatever it sends, on every page it sits on, forever.
1.8 million Android apps were scanned for hardcoded keys. Here is how to check yours.
Finding secrets in shipped apps is now a cheap, automated pipeline. Anything compiled into an APK, an IPA or a JavaScript bundle should be treated as already published.
OpenAI's Agents API will hold your agent state. What breaks if you ever need to leave.
Two major providers moved into the agent state layer in the same week. A managed harness is a real shortcut, as long as you keep a copy of what it holds.
Meta's Muse agent can now check out at your store. What merchants should change.
Agent purchases are arriving through wallets and single-use cards, not through merchants adopting a new protocol. Many merchants will receive them without choosing to.
What Brevo's SSO incident teaches about multi-tenant SAML and hijacked sending accounts.
One incident, two lessons: why email authentication did not help, and the tenant-scoping mistake anyone shipping SSO can make.
Cloudflare now sorts bots into Search, Training and Agent. What it means for your site and your agent.
The same change lands on two audiences. Site owners can now accidentally block search; agent builders will find more doors closed.
OpenAI has announced ten dated deadlines between 23 October 2026 and 1 April 2027. Here is the calendar.
Ten dated deadlines in six months, every one announced in public. The failure mode is never the notice. Updated 19 October with the entries added since September.
Nvidia bought Hugging Face. Your open-weight fallback is now a vendor relationship.
The commitments say nothing breaks. The structural change is that "we can always self-host" is now a dependency on one vendor rather than on a neutral commons.
The Videos API goes away on 24 September and OpenAI names nothing to move to.
Every other deprecation on OpenAI's page offers a migration target. This one does not, which makes it a different kind of problem.
Whisper shuts down on 26 February. The risk is not the deadline.
Five months is a generous window. Whisper is also typically wired into a background job that fails into a queue rather than into a user's face.
The Assistants API is gone. Your app may not have told you yet.
It shut down on 26 August 2026. The replacement is not a drop-in, and the most common migration mistake changes your model's behaviour without throwing an error.
One Copilot code review costs 13 requests. Here is the rest of the maths.
Copilot now bills on usage rather than seats. The headline change is simple. The multipliers underneath it are where teams get surprised.
Row-level security is on by default now. That is not the same as being protected.
Lovable fixed the default. The gap that actually leaks data was never the default, it was the policy, and no platform can write that for you.
Your model comparison is measuring the wrong number.
Every price list is per token. Your bill is per finished piece of work. Those two numbers can rank models in opposite orders.
An agent with production log access is a new identity. Treat it like one.
Always-on agents that read production logs are arriving fast. The access-control question they raise is old and well understood, which is the good news.

Open the tool.

Ten production categories, three minutes, and a ranked list of what to fix first.

Check your own stack