gemini-2.5-flash vs gemini-2.5-flash-lite
gemini-2.5-flash vs gemini-2.5-flash-lite: $0.3/$2.5 vs $0.1/$0.4 per 1M, the same workload priced on both; gemini-2.5-flash-lite is 76% cheaper per request.
| gemini-2.5-flash | gemini-2.5-flash-lite | |
|---|---|---|
| Provider · tier | gemini · fast | gemini · fast |
| Input | $0.3 | $0.1 |
| Cached input | $0.03 | $0.01 |
| Cache write | none | none |
| Output | $2.5 | $0.4 |
| Long-context tier | none | none |
| Per request (2,000 in / 300 out) | $0.00135 | $0.00032 |
| Per month at 100k requests | $135 | $32 |
| …with the static prefix cached | $95 | $19 |
| Cheaper sibling (cascade) | gemini-2.5-flash-lite | — |
Through TokenZero
Point your SDK at the gateway and keep both keys; the cache formatter, response cache and advisory routing act on every request, and each one comes back with a signed receipt showing the list-price baseline, actual cost and the saving.
OPENAI_BASE_URL=https://tokenzero.sh/w/<key>/v1 ANTHROPIC_BASE_URL=https://tokenzero.sh/w/<key>
Questions
Which is cheaper, gemini-2.5-flash or gemini-2.5-flash-lite?
At list prices (table 2026-10-26) gemini-2.5-flash-lite is 76% cheaper per request on a 2,000-in / 300-out workload. Quality is a separate question: TokenZero's cascade only routes to a sibling it scores as sufficient and measures parity with shadow evaluation.
Where do these prices come from?
The providers' own pricing pages, re-verified on 2026-10-26; the gateway signs receipts with the same table.