LLMIntel
OverviewLive demoCatalogCompareMCPPricingChangelogDocs
Start free
LLMIntel

A verified, normalized feed of AI model lifecycle events across every major provider, so a deprecation shows up on your roadmap instead of in your error logs. Plus runtime telemetry for what those models actually cost you.

Questions? support@llmintel.ai

Product
  • Pricing
  • Compare models
  • Azure OpenAI retirements
  • Dashboard
  • Changelog
  • Contact support
Developers
  • Quickstart
  • Model catalog
  • What’s retiring
  • MCP server
  • API reference
  • OpenAPI spec
  • Lifecycle RSS feed
  • @llmintel/telemetry
Free & open data

The model catalog is a normalized, machine-readable source of truth for AI model lifecycle events. It is free via the public API, and every record links to the primary provider source it came from.

© 2026 Alex Tsimbalistov. All rights reserved.
LLMIntel
OverviewLive demoCatalogCompareMCPPricingChangelogDocs
Start free

Find out what your GenAI actually costs

Your provider bill is one number a month. It will not tell you which app, which environment, or which model spent it. One line of code meters every call across OpenAI, Anthropic, Azure, AWS Bedrock, and Google, then shows you real spend per app, model, and environment — plus cheaper on-par models, and a warning before one you depend on retires.

See a live demoStart freeBrowse the free catalog

Free under $300/mo of tracked spend, no card. The demo needs no account, and neither does the catalog, the API, or the MCP server.

// meter every call your app makes
instrument(new OpenAI(), { environment: "prod" })
// or just read the free catalog, no key
curl llmintel.ai/v1/models/gpt-4o
All sources up to date
Last checked 4 hr ago
OpenAI4 hr ago
Anthropic4 hr ago
Azure AI Foundry4 hr ago
AWS Bedrock4 hr ago
Google4 hr ago
Cohere4 hr ago

Sources are re-checked at least every 24 hours. Status API

287
Models tracked
15
Deprecated
42
Retiring ≤ 90 days
66
Retired

Retiring soon

Every deadline →
claude-sonnet-4-5-20250929active
Anthropic
2026-09-29retires today
amazon.nova-canvas-v1:0retiring
AWS Bedrock
2026-09-30in 1 day
amazon.nova-reel-v1:0retiring
AWS Bedrock
2026-09-30in 1 day
amazon.nova-reel-v1:1retiring
AWS Bedrock
2026-09-30in 1 day
gpt-4o (2024-05-13)retiring
Azure AI Foundry
2026-10-01in 2 days
gemini-2.5-flash-imageretiring
Google
2026-10-02in 3 days

All models

Browse & filter all 287 →

Search and filter the full feed by provider and lifecycle state, with deprecation dates, retirement dates, and recommended replacements.

Stop your coding agent shipping a dead model id

Coding agents learned their model ids from a training snapshot, so they confidently write ids that stopped answering months ago. The LLMIntel MCP server adds a live lookup before the code lands: is this id still valid, when does it stop working, and what replaces it.

// .cursor/mcp.json
{
  "mcpServers": {
    "llmintel": {
      "command": "npx",
      "args": ["-y", "@llmintel/mcp"]
    }
  }
}
Ask: “is claude-sonnet-4-20250514 still safe to use?”
DO NOT USE — this model is retired;
API calls to it fail.

Provider: anthropic
Lifecycle state: retired — retired; calls fail
Deprecated: 2026-04-14 (105 days ago)
Retirement: 2026-06-15 (43 days ago)

Source: docs.anthropic.com/en/docs/about-claude
        /model-deprecations
Provider's own term: "Retired"
Set up the MCP server →Or call the REST API

Why this data is different

Anyone can scrape a table. The hard part is normalizing six vocabularies into one state machine and being right often enough that you'd page someone on it.

One lifecycle vocabulary

OpenAI says “shutdown”, Anthropic runs a four-state lifecycle, Azure publishes a retirement table, Bedrock says “Legacy”. All of it maps to one documented state machine: active → deprecated → retiring → retired.

Every record cites its source

Every record keeps the provider's verbatim term and a link to the exact page it came from. Parser changes go through a human review queue before publishing, so a page restructure never silently drops a retirement.

Checked hourly, publicly

Every collector run is recorded whether or not anything changed, so “last checked” is always honest. See it live at /v1/status.

Then find out what those models cost you

The catalog tells you what's changing. Add one line of telemetry and it tells you what it's costing. instrument(new OpenAI()) meters the models your app actually calls (metadata only, never prompts) and turns that into a live cost breakdown by app, environment, and tag. Switch suggestions are priced against your own token mix, so you get “save ~$1,840/mo” rather than “80% cheaper”.

Free under $300/mo of tracked spend, and retirement alerts for the models you actually run are free on every plan.

See a live demo →2-minute quickstart

Free to start. Priced to pay for itself.

The catalog

The model catalog, the REST API, and the MCP server are free forever and need no account or key. The cost dashboard and optimization suggestions are free too, while tracked spend stays under $300/mo.

Browse the catalog →
Running in production

Above the free ceiling, plans start at $29/mo and scale with your spend, staying a small single-digit-percent slice of the model bill they help you cut. One good switch usually pays for the year.

Compare plans →
LLMIntel

A verified, normalized feed of AI model lifecycle events across every major provider, so a deprecation shows up on your roadmap instead of in your error logs. Plus runtime telemetry for what those models actually cost you.

Questions? support@llmintel.ai

Product
  • Pricing
  • Compare models
  • Azure OpenAI retirements
  • Dashboard
  • Changelog
  • Contact support
Developers
  • Quickstart
  • Model catalog
  • What’s retiring
  • MCP server
  • API reference
  • OpenAPI spec
  • Lifecycle RSS feed
  • @llmintel/telemetry
Free & open data

The model catalog is a normalized, machine-readable source of truth for AI model lifecycle events. It is free via the public API, and every record links to the primary provider source it came from.

© 2026 Alex Tsimbalistov. All rights reserved.