We run a document-heavy assessment pipeline on the Gemini API. Each job sends the same large corpus to many batch calls. On Gemini 3.8 Flash, explicit context caching means we upload the documents once and every batch reuses them at the cached rate.
We tested Gemini 4 Hydrogen on the same pipeline and the same documents:
- Creating the cache fails: 400 INVALID_ARGUMENT: Explicit caching is not supported for models/gemini-4-hydrogen.
- The caching docs confirm explicit caching “is not supported… for Gemini 4 models”. They give no reason, no alternative with guaranteed behaviour, and no roadmap.
- Implicit caching covered about 4% of our input tokens on one lens: 0.9M cached out of 22.6M.
- Cost per call: $0.23 on 3.8 Flash, $0.88 on Hydrogen, at the same list price.
The issue is control. With explicit caching we decide what is cached and know what we will pay. With implicit caching, Google decides, the docs promise only “cost savings… when a request hits the cache”, and the discount rate is no longer published.
This matters more because of how 3.7 Flash was retired: the endpoint now silently routes to 3.8 Flash. If 3.8 Flash is routed to a Gemini 4 model the same way, every production pipeline built on explicit caching loses it with no code change and no error, just a bill several times larger.
Google needs to restore:
- Explicit context caching on Gemini 4 models, or an equivalent with guaranteed hits (not ‘best effort’).
- The published discount rate and hit rules for implicit caching.
- No silent routing of a model that supports explicit caching to one that doesn’t, and advance notice before any routing change.
- A clear statement of how long 3.8 Flash will support explicit caching.
If anyone has a way around this, I’m all ears.