Which models are going away

Three ways a model leaves. One is announced and you can plan for it. One is not, and you find out when something breaks. And one is announced by the vendor while the catalogue keeps listing it, which reads like neither.

Announced end-of-life

The vendor published a shutdown date. If your product calls one of these, that date is your migration deadline.

Removed without an announcement

These were in the OpenRouter catalogue we check daily, and then they were not. The catalogue carried no shutdown date for them. This is the list that does not exist anywhere else, because it only exists if someone was watching on the day it happened. A model can leave an aggregator without its vendor retiring it, so confirm with your provider before you migrate.

Announced, and now gone

The vendor published a retirement date and the model has since left the catalogue. These are not silent removals and are kept out of that list, which would otherwise say something untrue about the vendor that did announce them.

Announced, then un-announced

The vendor published a retirement date for these and its page no longer carries one. The model is still listed and still callable; what changed is what the vendor says about it. A calendar cannot show you this, because a calendar renders the page as it reads today and today is when it stopped saying so.

Retired by the vendor, still in the catalogue

The vendor's own deprecation page says these are gone. The catalogue still lists them, so you can pin one today and be surprised later. Neither source shows this on its own - it is only visible when both are read.

2 of these are still served on a platform whose own end-of-life is later, so the catalogue may be routing there rather than selling a dead model. The catalogue does not name the provider behind an entry, so that cannot be settled from it - they are counted above rather than quietly dropped.

Both lists come from the OpenRouter catalogue, checked once a day since 2026-07-29. A model absent for a single check and back the next is treated as an outage, not a retirement, and is not listed here. The full catalog is free JSON - no key, no signup.

Check your own code against this

Reading a list is work. This does it for you: point it at a repository and it reports which models you actually call are gone, which shut down soon, and where in your files they are used.

curl -sO https://neosignal-ai.vercel.app/check.py
python check.py .

No key, no signup, no dependencies. It exits non-zero when something you call is gone or shuts down inside 30 days, so it fails a CI build before a model does - and it exits 2 rather than passing if it could not reach the data, because a check that did not run is not a clean bill.

It does not guess what a model id looks like. Both the prefixed and the bare spelling are matched, and a token is kept only if it is a real id - so a directory path or a variable name cannot be mistaken for a model.

Source, issues and the CI recipe on GitHub