Model IDs retired from the catalogue on 2026-09-14

Anthropic, Google AI and Mistral AI retired claude-3-5-sonnet-latest, gemini-embedding-001, pixtral-large-latest and claude-opus-4-1 from the catalogue on 2026-09-14. For teams with those exact IDs in production configuration, this is a migration task rather than a release-note detail.

These are catalogue retirements. The records establish that the IDs have left this catalogue; they do not establish the status of every direct or cloud-specific route a vendor may operate. What matters for an integration is that a configured identifier can no longer be treated as an available catalogue dependency.

Each retired ID needs an explicit replacement decision

The retirement records name a successor for every departing ID. claude-3-5-sonnet-latest points to claude-sonnet-5. gemini-embedding-001 points to gemini-embedding-2. pixtral-large-latest points to mistral-small-latest. claude-opus-4-1 points to claude-opus-5.

That is useful information, but it is not a compatibility statement. The supplied records do not describe endpoint compatibility, request or response formats, supported modalities, context windows, output behaviour, or the treatment of existing prompts and stored data. A replacement name tells an operator where to begin an assessment, not what can safely be assumed about the application around it.

Start with the literal model strings. Search application configuration, environment variables, deployment manifests, request builders, scheduled jobs, tenant-level settings and test fixtures for each retired identifier. Model IDs are often set outside the code path that initially made a request: a routing rule, a feature flag, a background worker or a saved user preference can keep sending an old name after the primary configuration has changed.

The affected IDs also call for different reviews. A system using gemini-embedding-001 should identify every indexing and retrieval workflow that refers to it. A system using either Anthropic ID should locate prompt templates, tools and evaluation suites pinned to the retiring name. A system using pixtral-large-latest should identify the workloads and request paths that select that string before assigning its named replacement.

The successor record is complete only for part of the migration

The supplied catalogue data provides current repricing records for claude-sonnet-5 and mistral-small-latest. That gives both replacements a measured pricing record alongside their role in the retirement list. Neither model appears in the added list for this reporting period, however: a price record and a new activation record are different kinds of evidence.

The added list contains gpt-6-astra, gemini-3.8-flash and gemini-omni-1.1-flash. No successor named in the retirement records appears there. For migration planning, that means the period's activation data does not provide an added-model event for any of the replacements.

gemini-embedding-2 and claude-opus-5 have a thinner record. They are named as replacements, but neither appears in the added list or the repriced list. The aggregate catalogue snapshot reports 100 models, with 88 servable and 12 not servable, but it does not expose a model-by-model status list. It cannot establish whether either named successor is currently catalogued or servable.

That distinction should remain visible in an engineering ticket. A named replacement with a current price record is one state. A named replacement with no individual activation or pricing record in the supplied data is another. Conflating the two can turn a straightforward identifier update into an unplanned dependency problem.

The price records answer a budget question, not a compatibility question

claude-sonnet-5 was repriced effective from 2026-09-14. Its input price is listed as 2, from 3, and its output price is listed as 10, from 15. The retirement record ties it to claude-3-5-sonnet-latest, so teams moving that configuration have a current successor pricing record to include in their cost review.

mistral-small-latest, the replacement named for pixtral-large-latest, also has a repricing record effective from 2026-09-14. Its input price is listed as 0.15, from 0.2. Its output price is listed as 0.6, unchanged from 0.6. Those are the current measured fields available for that successor; the supplied data does not provide a price comparison with the retired pixtral-large-latest ID.

The absence of a price record matters as much as a listed price. The supplied material has no repricing entry for gemini-embedding-2 or claude-opus-5. It also gives no pricing fields for the retired IDs themselves. A team cannot use this data to state a total migration cost, a saving or a cost increase for either path.

Keep budget controls separate from technical validation. Update alerts, quotas and chargeback labels when a replacement has a confirmed catalogue record and an approved configuration. Do not treat a lower or unchanged field in a repricing record as evidence that requests, prompts or outputs will behave the same way. The data does not make that claim.

Model IDs belong in an operational inventory

A retirement exposes a common weakness in model integration: model selection is often managed as a string rather than as a deployable dependency. A durable inventory should associate each configured model ID with the service that uses it, the endpoint it expects, the prompt or data flow it supports, its owner and the budget controls attached to it.

That inventory makes catalogue changes actionable. The owner of a service using claude-3-5-sonnet-latest can assess claude-sonnet-5 against the application's existing requirements. The owner of an embedding pipeline using gemini-embedding-001 can determine whether gemini-embedding-2 has a usable route before changing index or retrieval work. The owner of a workload using claude-opus-4-1 should not assume that claude-opus-5 is ready for selection merely because it is named as the replacement.

Testing should follow the same boundary. Validate the exact replacement ID that will be deployed, through the route and request construction used in production. Check model-selection fallbacks as well as the primary configuration. If the application persists model IDs in records, queues or job definitions, account for those references too; replacing a default does not alter already stored values.

The catalogue reports 67 models under /v1/chat/completions and 4 under /v1/embeddings, but those aggregate endpoint totals cannot establish an endpoint for a particular replacement. Treat endpoint suitability as a fact to verify from the available model record, not as something implied by a model family name or a vendor name.

The next catalogue changes should resolve the unlisted successor paths

The immediate watch item is an individual catalogue record for gemini-embedding-2 and claude-opus-5. In the supplied period, both are named replacement targets without an added-model record or a pricing record. Their appearance in a later activation or pricing update would turn an unresolved migration path into one with more operational detail.

Teams moving from claude-3-5-sonnet-latest and pixtral-large-latest should also monitor the existing successor records. claude-sonnet-5 and mistral-small-latest have measured prices effective from 2026-09-14, but the retirement data does not answer compatibility questions on their behalf. The safe response to a quiet deprecation is to find every old ID, record the named replacement, separate confirmed catalogue facts from missing facts, and make the change deliberately.