Latest snapshot 2026-03-30 02:54 Most recent stored public pricing point for this model.
Source Gemini Developer API Pricing Keep the source link below for manual verification when needed.
Cache support Listed Cached input pricing only appears when the source exposes it clearly.
Batch support 50% of normal Batch mode should not be mixed with realtime pricing assumptions.
Input price
$1.250000 per 1M tokens
Output price
$10.000000 per 1M tokens
Cached input
$0.125000 per 1M tokens
Blended price
$3.4375 75 / 25 input-output mix
Single request estimate $0.0121
Monthly estimate $3615.0000
Batch discount 50% of normal price
How to read this estimate The reference workload is a fast sanity check, not a forecast. If your prompt shape, cache ratio, or monthly traffic differs, jump to the calculator with this model preselected and adjust the assumptions there.
No delta yet Waiting for another snapshot A price change needs at least two recorded points. This model currently has too little history to show a delta or nothing has changed yet.

Only one stored point exists so far. Trend and change detection will become useful after later crawls add more history.

Captured at Input / 1M Output / 1M Cached / 1M Source
2026-03-30 02:54 $1.250000 $10.000000 $0.125000 Gemini Developer API Pricing

Source and limits

Source Gemini Developer API Pricing https://ai.google.dev/gemini-api/docs/pricing
Context window 1048576
Output limit 65536
Source note standard input=$1.25, prompts <= 200k tokens | $2.50, prompts > 200k tokens; standard output=$10.00, prompts <= 200k tokens | $15.00, prompts > 200k; cache=$0.125, prompts <= 200k tokens | $0.25, prompts > 200k | $4.50 / 1,000,000 tokens per hour (storage price)

When this model detail is enough

Use this page when you need a single-model read: current price, context limits, source traceability, and a lightweight history view without opening the full comparison workflow.

When to escalate to compare

If you are choosing between several plausible models, one detail page is not enough. Move to compare so every candidate runs against the same workload assumptions.

When to escalate to calculator

If finance or usage planning matters, use calculator next. That lets you replace the reference workload with your own request volume, cache ratio, and budget ceiling.