Quick answer
Gemini 3.8 Flash is the current default to test for new Google API workloads. Google’s active model route replaces the older 3.7 Flash and 3.6 Flash entries in our lifecycle data without changing the tracked Standard token rates from 3.7 Flash. That makes migration primarily a capability and compatibility decision, not a headline price-cut decision.
The chart, calculator, and table above read pricing.json at build time. Use the Google AI pricing page for the entire tracked catalog or the full AI pricing table for cross-provider comparisons.
Which Gemini model should you use?
| Workload | Start with | Escalate when | Measure |
|---|---|---|---|
| Classification, extraction, routing | Gemini 3.1 Flash-Lite | Validation or nuance fails | Valid records per dollar |
| Support, product Q&A, routine RAG | Gemini 3.8 Flash | Answer quality misses the target | Resolved requests per dollar |
| Multimodal app flows | Gemini 3.8 Flash | Complex interpretation needs Pro | Accepted outputs and latency |
| Premium RAG and document analysis | Gemini 2.5 Pro | Newer preview behavior is required | Supported claims per dollar |
| Frontier reasoning evaluation | Gemini 3.1 Pro Preview | Stable availability is mandatory | Correct decisions per dollar |
| Long-context review | A Pro route after tier modeling | Retrieval cannot shorten the prompt | Cost per accepted review |
Use Gemini 3.1 Flash-Lite for compact, mechanically checked utility calls. Use Gemini 3.8 Flash when a user sees the answer or the request combines text with image, audio, or video inputs. A Pro model belongs behind an evaluation gate: stronger reasoning is useful only when it improves the completed task enough to cover its higher token and latency cost.
Gemini 3.1 Pro remains a preview model in the current dataset. Gemini 2.5 Pro is an older route, but it can still be the safer comparison when a production team values established behavior over the newest preview. Pin an exact model ID rather than relying on an alias that can change underneath a deployment.
Context, caching, audio, and grounding
Pro billing changes when the input prompt crosses the provider’s long-context threshold. The live table includes separate Gemini 2.5 Pro rows for the normal and long-context tiers; use the official rate card to confirm the same threshold behavior for preview models. Retrieval, deduplication, and conversation summarization can keep many requests below the expensive tier without reducing answer quality.
Cached-token processing and cache storage are separate line items. A low cached-input rate does not make a long-lived cache free. Forecast the reusable prefix, expected hit rate, storage duration, invalidation frequency, and uncached remainder before claiming savings. Our cached tokens guide explains the break-even calculation.
Audio pricing can differ from text, image, or video input on some Gemini routes. Google Search and Maps grounding also add request- or query-based charges outside the token line. The calculator above estimates normalized token cost only, so a grounded or audio-heavy application needs those provider-specific charges added to its budget.
Free tier and hidden costs
Free access is model-, region-, and execution-class-specific. Treat it as an evaluation allowance, not a production budget. Confirm current eligibility, rate limits, data-use terms, and whether the exact model is available in the Gemini Developer API or Vertex AI route you plan to deploy.
The base token bill also omits several costs that commonly decide the real winner:
- retries after malformed structured output or tool failures
- grounding, retrieval, storage, and paid tool calls
- duplicated context and unused multimodal payloads
- fallback traffic sent to a second model or provider
- human review for customer-facing or regulated decisions
Track cost per accepted task rather than cost per call. A cheaper request is not cheaper if lower quality causes more retries, escalations, or manual correction.
A practical Gemini routing plan
Start with a production-shaped test set containing short prompts, long documents, multimodal requests, tool calls, invalid inputs, and cases that previously failed. Run Gemini 3.1 Flash-Lite, Gemini 3.8 Flash, and one Pro candidate with the same output schema, timeout, retry cap, and maximum response length.
Record task success, input and output tokens, cache hits, grounding calls, latency, retries, safety refusals, and review time. Then deploy the least expensive route that clears the quality floor and escalate only uncertain or high-value requests. Recheck the token calculator with the measured input-to-output ratio instead of a generic average.
Include one independent provider in the test so the evaluation does not become a choice among Google tiers only. Compare Gemini with OpenAI pricing and Anthropic pricing. For a managed open-model control, check Novita’s current model catalog and confirm the exact model, region, and live rate before testing.
Affiliate disclosure: we may earn a commission from the sponsored link above. It does not affect our pricing data or recommendations.
FAQ
Which Gemini API model is best for most developers?
Start with Gemini 3.8 Flash for user-facing and multimodal work. Use Gemini 3.1 Flash-Lite for simpler validated jobs and move to Pro only when your evaluation shows a worthwhile quality gain.
Did Gemini 3.8 Flash cut API prices?
The current dataset shows the same Standard token rates as the superseded Gemini 3.7 Flash route. Treat the change as a model migration and re-evaluate quality, latency, compatibility, and limits.
Does cached input always reduce the total Gemini bill?
No. Savings depend on eligible repeated input and actual cache hits, while cache storage and invalidation can add cost. Model both processing and storage before adopting a cache strategy.
Is grounding included in Gemini token pricing?
No. Search and Maps grounding can add separate request- or query-based charges, so the token calculator does not represent the entire grounded workload bill.
Does Gemini Pro have a free tier?
Availability varies by model and execution route. Check the current official row, limits, and terms before assuming preview, stable, Gemini Developer API, and Vertex AI access are interchangeable.
Bottom line
Gemini 3.8 Flash is the sensible production default to benchmark now, with Flash-Lite for validated utility work and Pro behind a quality gate. The winning route is the one with the lowest cost per accepted task after context tiers, cache storage, grounding, retries, and review time are counted.
Rates and lifecycle status were verified September 1, 2026 against the Data-owned live dataset and Google’s official Gemini API pricing. Recheck the provider rate card before signing a budget or launching production traffic.