The single biggest lever
Pro is ~22.5× more expensive per output token than Flash-Lite. Most of your traffic doesn't need Pro. A smart router that sends routine work to Flash-Lite, default work to Flash, and only-when-required work to Pro typically cuts production bills 70–90%.
Routing inputs
The decision is based on:
- Reasoning needed? Multi-step logic, code, math → Pro.
- Context size? > 200K tokens → Pro (only Pro handles long context well; Flash and Flash-Lite hit quality drops).
- Tool use? Complex multi-tool agentic loops → Pro. Simple single-tool calls → Flash.
- Latency? Sub-500ms requirement → Flash-Lite (smallest, fastest TTFT).
- Volume? High-volume simple tasks → Flash-Lite.
Real numbers
| Strategy | Relative cost | When |
|---|---|---|
| Always Pro | 1.0× | Maximum quality, no cost ceiling |
| Smart routing | ~0.3× | Most production apps |
| Flash-Lite only | ~0.04× | High-volume simple tasks |
| Caching enabled | ~0.1× per cached call | Repeated context (PDF Q&A) |
| Batch API (offline) | 0.5× | Async pipelines |