AI News

Gemini 2.5 Flash-Lite cache-read price history

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

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

Googleprovider
gemini-2.5-flash-litestable identity
cache readprice component
USD / 1M tokensunit
243retained observations
2machine-detected states

Identity and scope

The stable API model ID is gemini-2.5-flash-lite. This series covers standard paid-tier context-cache reads for text, image and video tokens; audio, storage and alternative consumption tiers are separate prices.

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

Google cut this cached-input component from one quarter to one tenth of the model’s $0.10 standard text-input rate. The before and after captures are less than ten hours apart.

Old price last seen Old New price first seen New Verification
October 24, 2025
last old-price capture
$0.025 October 24, 2025
first new-price capture
$0.01 60% cut; both bounding captures are from October 24, 2025 UTC.

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.025 USD machine-only state archive
06c6f09c59f86353…
2 $0.01 USD bounds a verified episode archive
b8a274c43b5e8dad…

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.