Gemini Context Caching: 95% Off Your Input Bill — and Three Ways It Bites Back

Verdict: If you're running long system prompts or agentic workflows on Gemini 4 Argon, context caching is the difference between a survivable December bill and a painful one — because on December 1, Argon's input price doubles to $4/1M and caching is the only discount that doesn't depend on the promo. Verified via OpenRouter's API today: cached input reads cost $0.10 per 1M tokens vs $2.00 uncached — 95% off. Implicit caching (automatic, no code) gives a documented 90% discount. But Google's cache has teeth: explicit caches bill for their entire TTL even if you delete them early, and at least one model (3.1 Flash-Lite) silently lost its implicit discount around June 30. Caching on Gemini is real money saved — with an audit requirement attached.

Two caches, two contracts

Gemini API has two caching mechanisms and they bill differently. Explicit caching is the one you manage: you create a cache, set a TTL, and pay storage for every minute it lives. Reads are cheapest — $0.10/1M on Argon (verified today), with a one-time cache write at $0.1875/1M. Implicit caching is the one you don't: Google detects repeated prefixes automatically and applies a documented 90% discount on cached tokens with no storage fee and no code. Implicit requires a minimum prompt size (historically 2,048 tokens on Flash-class models — below that, nothing caches), so tiny prompts see zero benefit from either mechanism.

The break-even math on explicit caching is unforgiving: cache storage bills per minute, so a cache only pays off if you read it enough times within its TTL. Long, stable system prompts — the agent-workflow case — hit break-even in a handful of calls. Per-user chat sessions almost never do.

The teeth: three ways the discount bites back

TTL billing doesn't stop when you do. On Google's own developer forum, a user documented that deleting an explicit cache entry after 15 minutes of a 1-hour TTL still bills the full hour. If your pipeline creates and discards caches programmatically, TTL length is a cost decision, not a convenience setting — set it to the shortest window your workload tolerates.

Implicit discounts can vanish without notice. A June 30, 2026-era forum report says implicit caching stopped applying its discount on 3.1 Flash-Lite for at least one project — same prompts, same code, discount gone. Implicit caching is a behavior, not a contract. The only safe posture is watching your bill, not trusting the feature flag.

The 90% number moved before and will move again. Implicit caching launched in May 2025 at a 75% discount and was raised to 90% (the increase Reddit picked up this month). That history cuts both ways: it can improve, but it is a platform-controlled knob on your cost base.

What this means after December 1

When Argon's uncached input goes from $2 to $4/1M, the explicit cache read price — if it holds at $0.10 — becomes a 97.5% discount instead of 95%. Whether it holds is an open question; promo-period pricing has a habit of repricing together, and Google's pricing page is not reachable from our network today to check for a posted post-promo cache price. Assume the cache discount percentage stays roughly constant and the absolute number doubles with it — then caching's relative value is unchanged, which is exactly the point: the promo expires; the caching lever doesn't.

My take for agent builders: design for implicit caching first (zero code, zero storage risk), and reach for explicit caching only when you have a genuinely hot, stable, giant prefix — and then set the TTL like you're paying for it, because you are. And whatever you do, diff your bill weekly; the 3.1 Flash-Lite silent-expiry story is why.

Dated caveat (2026-10-20): prices from OpenRouter's API today ($2/$10, cache read $0.10, cache write $0.1875 on gemini-4-argon); implicit discount and TTL-billing behavior from Google's docs and forums via snippets — ai.google.dev and cloud.google.com are not directly reachable from our network, and Google's own pages are the authority when they disagree with relays. The December 1 promo expiry is relayed from launch coverage. I run DeepSeek-adjacent workloads, not Gemini production traffic — the TTL break-even advice is engineering judgment, not my lived bill.

Sources: OpenRouter models API (queried 2026-10-19 and 2026-10-20); Google Cloud caching docs; Vertex AI context caching blog (Oct 15 update); Google AI developer forum threads (linked inline); r/Bard implicit-discount thread.

Related: Gemini 4 Argon API Pricing: The Intro Rate Doubles on December 1 · Gemini 3.8 Flash Pricing · DeepSeek Off-Peak Pricing Explained