deprecations.info's homepage, fetched on October 20, 2026, calls itself AI Deprecations Feeds. It says it tracks deprecations from OpenAI, Anthropic, Google AI/Gemini, Google Vertex AI, AWS Bedrock, Cohere, Groq, xAI, and Azure, as a JSON API, a JSON Feed, and RSS. It says a model shows up when the provider announces a shutdown.
The homepage says that when a provider publishes different dates by region, the feed keeps one row per model id and uses the earliest published deprecation date and the earliest shutdown date. It links the GitHub repo deprecations/deprecations-rss and shows how to follow the RSS URL in Feedly, an email-from-RSS service, or Slack.
https://deprecations.info/v1/feed.json, fetched the same day, is JSON Feed 1.1. The title is AI Model Deprecations. The author name in the file is deprecations.info. Each item has id, url, title, content_text, date_published, tags, and a _deprecation object with provider, model_id, shutdown_date, deprecation_date, announcement_date, replacement_models, first_observed, and last_observed. The first items are OpenAI model ids whose url is an OpenAI deprecations anchor. https://deprecations.info/v1/providers.json lists those nine providers and the official URL for each.
Side by side
What deprecations.info published on October 20, 2026, and what SunsetDiff publishes in this build.
Topic
deprecations.info
SunsetDiff
Shape of the data
A feed item per announcement: model id, deprecation date, shutdown date, replacement model ids, first and last observed days, and the provider URL.
When both models are in the dataset, a migration page shows input, output, and cached price per 1M tokens, an example monthly cost, context window, max output, capability fields that differ, API changes with a source link, before/after code in Python, TypeScript, and curl, and a checklist. Empty cells say Not published. Full records also keep status, shutdown_date_kind, and specs.
Providers on the feed
Nine: OpenAI, Anthropic, Google, Google Vertex, AWS Bedrock, Cohere, Groq, xAI, and Azure.
The providers in this build are listed at the top of this page.
Regional dates
The homepage says regional dates collapse to one row, using the earliest published dates.
Bedrock rows can keep region_or_platform_notes when the official page limits the date to listed regions.
Other files
The homepage documents /v1/feed.json, /v1/feed.xml, and /v1/providers.json.
Static files, no API key: /data/models.json, /data/deprecations.csv, /data/changelog.json, /dataset/sunsetdiff.json, /dataset/sunsetdiff.csv, /api/v1/, /feed.xml, and /deadlines.ics. License CC BY 4.0. Publisher: SunsetDiff. The scan page gives a ripgrep pattern for retiring model ids. It runs on your machine. The page does not upload a repository.
Sources checked October 20, 2026
deprecations.info homepage. Checked 2026-10-20. Provider list, JSON Feed and RSS, the regional-date note, and the GitHub repo link.
JSON Feed. Checked 2026-10-20. JSON Feed 1.1 fields and the _deprecation object.
providers.json. Checked 2026-10-20. Nine providers and their official documentation URLs.
SunsetDiff tracks them at sunsetdiff.com. It records the shutdown date, the official replacement, and the published change in price, context, and code. The same records are free JSON and CSV files under CC BY 4.0. Publisher: SunsetDiff.
Is there an API for LLM model shutdown dates?
SunsetDiff publishes static files. They need no API key. upcoming.json lists shutdowns in the next 90 days. models.json is the full model list. Field names and examples are on the API docs.
How does SunsetDiff compare with deprecations.info?
deprecations.info is a JSON Feed and RSS of shutdown announcements, with replacement ids and observed dates. SunsetDiff publishes those dates inside full model records and migration diffs, plus CSV, an ICS calendar, and a local code scan.