AI News

Gemini 2.5 Flash cache-read price history

Kingy.ai Price History Library · evidence observed through August 2, 2026

Gemini 2.5 Flash cache-read price history tracks cache read list pricing for gemini-2.5-flash. It publishes 1 editorially verified episode while preserving the broader machine timeline as a separate evidence layer.

Googleprovider
gemini-2.5-flashstable identity
cache readprice component
USD / 1M tokensunit
287retained observations
2machine-detected states

Identity and scope

The stable API model ID is gemini-2.5-flash. The tracked component is standard paid-tier context-cache reads for text, image and video tokens, not audio caching, cache storage, Batch, Flex or Priority service.

Scope boundary. Values are published list prices in USD per million native tokens for the named component. They do not establish negotiated, enterprise, regional, cloud-marketplace or promotional rates. The archive records when a price was observed, not the exact moment a provider changed billing.

Editorially verified change

The standard context-cache read rate fell 60% while the model ID stayed stable. Cost comparisons that retain the earlier $0.075 rate overstate the cached-input portion of later Gemini 2.5 Flash workloads.

Old price last seen Old New price first seen New Verification
October 5, 2025
last old-price capture
$0.075 October 9, 2025
first new-price capture
$0.03 60% cut; the archive bounds the edit to a 3-day interval.

Machine-detected state timeline

The rows below come from the scope-safe machine series. A changed value is not automatically an editorial change. Only rows tied to the verified brackets above support the page’s change claim; the others remain observations or held transitions.

State First observed Value Editorial status Lineage
1 $0.075 USD machine-only state archive
2afcbb1877ed4bcb…
2 $0.03 USD bounds a verified episode archive
279a1eddeaa045f0…

Source and archive lineage

How to use this history

Use the verified row when reconstructing a dated standard-list-price estimate. Use the machine timeline to audit extraction and locate captures, not to infer billing scope or a precise effective timestamp. Recheck the provider’s current documentation before making a live purchasing or architecture decision.