The Gemini API offers a variety of optimization mechanisms to help you balance speed, cost, and reliability based on your specific workload needs. Whether you're building real-time conversational bots or running heavy offline data-processing pipelines, choosing the right paradigm can significantly cut costs or boost performance.
| Feature | Standard | Flex | Priority | Batch | Caching |
|---|---|---|---|---|---|
| Pricing | Full Price | 50% discount | 75% to 100% more than standard | 50% discount | 90% discount + Prorated token storage |
| Latency | Seconds to minutes | Minutes (1–15 min target) | Seconds | Up to 24 hours | Faster time-to-first-token |
| Reliability | High / Medium-high | Best-effort (Sheddable) | High (Non-sheddable) | High (for throughput) | N/A |
| Interface | Synchronous | Synchronous | Synchronous | Asynchronous | Saved state |
| Best use case | General application workflows | Non-urgent sequential chains | Production, user-facing apps | Massive datasets, offline evals | Recurring queries over same file |
Inference service tiers (Synchronous)
You can shift between reliability-optimized and cost-optimized synchronous traffic
by passing the service_tier parameter in your standard generation calls.
Standard inference (Default)
The standard tier is the default option for sequential content generation. It provides normal response times without extra premiums or heavy queuing.
- Reliability: Standard criticality
- Price: Standard pricing.
- Best For: Most interactive day-to-day applications.
Priority inference (Latency-optimized)
Priority processing routes your requests to high-criticality compute queues. This traffic is strictly non-sheddable (never preempted by other tiers) and offers the highest reliability. If you exceed dynamic Priority limits, the system will gracefully downgrade the request to Standard processing instead of failing with an error.