An alias that moves, or an identifier that does not
The deprecations table lists specific identifiers with dates, which means a caller who pinned one can match a published date to their own code. A caller using a moving alias cannot: the alias is not on the table, and what it points at can change without anything on that page moving. As of 2026-09-22.
| What the page is asked | What Gemini API publishes | What that leaves open |
|---|---|---|
| Is a starting tier stated | Not applicable, a request names what it wants | The platform does not choose for you |
| What the table lists | Specific identifiers, each with a date | Aliases do not appear on it |
| What a pinned identifier gives | A row you can match to your own code | Plus a date that is stated as the earliest |
| What an alias gives | Whatever it points at that day | With no row on the table to watch |
Inclusion rule. Filled when the entry's own public page says which model a new project starts on, or when a single-model menu makes the answer follow from the list having one line. Order. What does not apply first, then what each kind of caller can see.
1The table only works for callers who pinned
A deprecations page listing exact identifiers is a planning document for anybody whose code contains one of those strings. For anybody using a convenience alias it is a list of names they do not use.
So the same page is a schedule for one caller and background reading for another, and nothing about it announces which kind of caller you are. That is the finding this reading exists for.
2An alias is a default that moves without a notice
An alias is the closest thing to a default this layer offers, and its whole purpose is to change what it resolves to. When it moves, output can change with no row on the deprecations table altering at all.
That is the invisible version of the event this register was built to make visible, and it happens at the caller's own convenience setting rather than at a vendor's announcement.
3Pinning has its own cost, stated on the same page
A pinned identifier can be matched to a date, and the date is described as the earliest a model might be retired. So pinning buys a known runway of uncertain length rather than certainty.
The pinning page sets out what a version identifier covers and what it leaves moving. Both halves matter here, because this is the entry where a caller genuinely has the choice.
- veo-3.0-generate-00130 June 2026veo-3.0-fast-generate-001 and veo-2.0-generate-001, shutdown date
- What a date in that table commits toThe shutdown dates listed indicate the earliest possible dates on which a model might be retired
4Sources
Read from the deprecations page on ai.google.dev, 2026-09-22. The whole entry is on Gemini API, and the column it sits in is on Default tier. Same column, other entries: Wan-AI, SceneMixer.