Before Gemini traffic reaches production, pick the route and the model from tests on your own workload, put shared content first so it caches, and send work that can wait to Batch. Then set project spend caps and name an owner for Google's model retirements.
When you need this
- A feature built on Gemini is moving from an AI Studio prototype to production traffic.
- The monthly bill grows faster than usage, or a Flash generation change moved your costs.
- A model you depend on is deprecated, or requests to it are routed to a successor.
Evaluation criteria
Setup: one project per workload
Can you see and cap spend and limits for each product?
Look forA Google Cloud project per workload. Limits apply per project, so every key in a project shares them. Each project has a key restricted to the Gemini API and its own spend cap, set in AI Studio.
Route: AI Studio key or Agent Platform
Do you need service accounts, regional endpoints, Cloud billing, or reserved capacity?
Look forThe Developer API for fast setup and the free tier, and Gemini Enterprise Agent Platform when you need Google Cloud controls. Several builders moved to the Agent Platform after overload or spend-cap errors, and one still hit persistent rate-limit errors there.
Model choice: evaluations per task
Which model passes your own test set at the lowest cost per completed task?
Look forRun a held-out evaluation set on 3.8 Flash and 3.5 Flash-Lite, counting thinking tokens as output. MLH found no dangerous Flash-Lite routing calls in its first round. Another builder lost 6% to 20% accuracy on 20 PDFs with newer models at minimal thinking. Test the thinking setting too.
Cost control: cache and batch
Does the stable part of every prompt come first, and can some work wait?
Look forPut large shared content at the start of prompts for implicit caching. 3.8 Flash requires at least 4,096 tokens. Use Batch or Flex at half price for work that can wait. One builder moved a document tool from Mistral's OCR API to Gemini Flash and pays half the inline price through Batch.
Reliability: retries and a fallback
What happens to your feature when Gemini returns 503 or 429?
Look forRetry with exponential backoff and cap output length. Keep a second model or provider available for overloads. One team measured a 37% failure rate from overload errors over 30 days on 3.6 Flash.
Review practice: track retirements
Who owns model retirement dates and re-runs evaluations before a switch?
Look forModel names kept in configuration, the deprecations and release-notes pages watched, and evaluations rerun before switching. Pre-release models have shut down two weeks after notice. Gemini 2.5 Pro, Flash, and Flash-Lite reached their Agent Platform retirement date on October 20, 2026, and Google names 3.8 Flash as a replacement.
Questions to ask vendors
- Which usage tier is each project on, and what monthly cap applies to its billing account?
- Which of our requests run on the free tier, and does any of that traffic carry customer data?
- Which of the models we call are pre-release models, and what are their earliest shutdown dates?
- Does our Google Cloud agreement give us Provisioned Throughput or committed-use pricing on the Agent Platform?
Red flags
- One API key shared by every product and team, with no restrictions and no project spend cap.
- A production feature on a pre-release model, or on a model string that Google now routes to a successor.
- Thinking tokens left out of the cost model, though they bill as output.
- No retry or fallback for 503 overloaded errors.
Products in this piece
Sources
- Official documentation
- 12
- Public source
- 7
- Gemini API docs: Rate limits
- Gemini API docs: Using Gemini API keys
- Gemini API docs: Gemini Developer API vs. Gemini platform
- Gemini API docs: Models
- Gemini API docs: Gemini Developer API pricing
- Gemini API docs: Context caching
- Gemini API docs: Batch API
- Gemini API docs: Flex inference
- Gemini API docs: Troubleshooting guide
- Gemini API docs: Gemini deprecations
- Gemini API docs: Release notes
- Agent Platform docs: Model versions and lifecycle
- Swift (Major League Hacking): I got Jev to zero mistakes. I'm still using Flash-Lite. (Oct 8, 2026)
- Google AI Developers Forum: An evaluation of 20 PDFs on the pre-release Gemini 3 Flash and newer models (Sep 14, 2026)
- Hacker News comment on moving a document tool from Mistral OCR to Gemini Flash and Batch (Sep 8, 2026)
- Google AI Developers Forum: Persistent 37% UNAVAILABLE (503) on gemini-3.6-flash (Aug 28, 2026)
- junhee916: Google AI Studio 503 Errors? Migrated to Vertex AI (Jun 6, 2026)
- Google AI Developers Forum: Persistent 429 on Vertex AI after migrating from AI Studio (Mar 17, 2026)
- Google AI Developers Forum: Gemini model lifecycle is incompatible with production workloads (May 11, 2026)