Skip to content
Hugin
An empty aisle runs between tall server racks under exposed silver ductwork.

Hugin News

Google schedules Gemini 2.5 and Omni requests to switch models and billing rates in December

2 min read

Original editorial artwork from the Hugin archive; a generated server-room illustration, not a photograph of Google's infrastructure.

Google says Gemini API requests to Gemini 2.5 Pro and Flash will automatically route to named replacements at their rates on December 1; Omni 1.1 Flash follows December 3. The deprecations table separately lists December 18 for three speech previews and March 31, 2027 for a native-audio preview, under its earliest-possible-date caveat. No endpoint or customer bill was tested.

googlegemini-apimodel-routingbillingdeveloper-tools
source receipts
2
source host
1
read time
2min
primary source
Linked

Google has scheduled automatic model and billing switches for three existing Gemini API identifiers in December. Its release notes say requests using the older names will go to their named replacements and be billed at those replacements' rates.

Two switches on December 1

The November 2 release notes say gemini-2.5-pro requests will automatically route to gemini-3.8-flash, while gemini-2.5-flash requests will route to gemini-3.5-flash-lite, effective December 1, 2026.

Google tells developers to update each model string before December 1 and review the respective migration guide. The announcement identifies breaking API changes involving function calling, validation of thought_signature, the replacement of thinking_budget by thinking_level, and removed sampling parameters and prefilled model turns.

The deprecations page says access to the two older models is limited to existing users who previously used them. It separately says gemini-2.5-flash-lite is not deprecated and remains available through the API until further notice. Similar names do not give those three models the same schedule.

Omni follows on December 3

The November 5 release notes announce that requests to gemini-omni-1.1-flash will automatically route to gemini-omni-1.2-flash at the latter's rates, effective December 3, 2026.

That is a separate model family and a separate date. The announcement does not say that every Gemini API request switches on December 1 or that developers must create a new account.

Audio previews have separate schedules

Read November 14, the deprecations table lists December 18, 2026 for gemini-3.1-flash-tts-preview, gemini-2.5-flash-preview-tts and gemini-2.5-pro-preview-tts. It names gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts as replacements.

For gemini-2.5-flash-native-audio-preview-12-2025, it lists March 31, 2027, with gemini-3.8-live as replacement. The separate gemini-3.1-flash-live-preview row names that same replacement but gives no announced shutdown date. These are current page readings, not evidence of an implemented shutdown or a date when the page changed.

A schedule, not a tested bill

Google's deprecations page generally describes listed shutdown dates as the earliest possible dates and says users will receive advance notice of an exact shutdown. A dated automatic-routing announcement is more specific about what happens to requests using an old identifier; it should not be reduced to a claim that all old endpoints simply stop answering.

These records establish Google's announced destinations, dates and billing basis. They do not establish output equivalence, successful migration of a particular application, or the amount of a customer's next bill. No endpoint or invoice was tested for this report.

Source links