Last verified: July 21, 2026
Short path: Compare live Gemini catalog prices on our Gemini API hub or migrate on the cheap Gemini API page.
Developers comparing Gemini Pro vs Flash usually face the same production question: Flash is cheaper and often faster, but Pro handles long context and harder reasoning. Picking Pro by default is a common reason Gemini API bills spike. Picking Flash for everything is a common reason quality and agent reliability drop.
This guide compares Gemini 3.1 Pro Preview, Gemini 3.5 Flash, and Gemini 3 Flash for real-time API workloads — token prices, latency patterns, escalation rules, and runnable Python on LumeAPI's OpenAI-compatible endpoint.
LumeAPI is an independent third-party gateway. It is not Google or an official Google billing channel.
Quick Answer
| Question | Practical answer |
|---|---|
| 3.5 Flash vs 3.1 Pro? | Default to 3.5 Flash for chat, agents, and coding at volume. Escalate to 3.1 Pro for long-document RAG, hard reasoning, or when Flash fails evals. |
| Is Flash always faster? | Usually yes for comparable prompts — Pro runs heavier reasoning. Slow feelings often come from thinking tokens, long context, or using Pro where Flash suffices. |
| Cheapest Gemini text tier? | Gemini 3 Flash for classification, routing, and high-QPS subtasks. |
| LumeAPI model ids | gemini-3.5-flash, gemini-3.1-pro-preview, gemini-3-flash |
For 100M input + 20M output tokens per month (standard rates):
| Model | Google standard | LumeAPI catalog | Typical use |
|---|---|---|---|
| Gemini 3.1 Pro | ~$440 | ~$264 | Long context, hard steps |
| Gemini 3.5 Flash | ~$330 | ~$198 | Production default |
| Gemini 3 Flash | ~$110 | ~$66 | Volume / routing |
Gemini 3.5 Flash vs 3.1 Pro — capability and cost
Gemini 3.1 Pro Preview
Google positions Pro for complex multimodal understanding, difficult coding, and agentic workflows.
Google standard (≤200K prompt tokens):
- Input: $2.00 / 1M tokens
- Output (incl. thinking): $12.00 / 1M tokens
LumeAPI catalog:
- Input: $1.20 / 1M
- Output: $7.20 / 1M
Use Pro when:
- Retrieved context regularly exceeds what Flash handles reliably
- Multi-step software engineering fails on Flash in your eval set
- A failed Pro hop is cheaper than repeated Flash retries
Gemini 3.5 Flash
Google describes 3.5 Flash as its speed-oriented intelligent tier — stronger than 3 Flash, cheaper than Pro for many workloads.
Google standard:
- Input: $1.50 / 1M
- Output: $9.00 / 1M
LumeAPI catalog:
- Input: $0.90 / 1M
- Output: $5.40 / 1M
Use 3.5 Flash when:
- Interactive chat and copilots need strong quality at scale
- Agents need tool calling without Pro-level reasoning every hop
- You want one default Gemini id before escalating
Gemini 3 Flash
The budget tier for classification, summarization, and agent subtasks.
LumeAPI catalog: $0.25 / $1.50 per 1M input/output.
Speed: why Gemini API feels slow
Searches for gemini api slow often trace to configuration — not a broken endpoint.
| Cause | What to check |
|---|---|
| Wrong tier | Pro on every hop adds latency vs Flash |
| Thinking tokens | Billed as output; longer generations feel slower |
| Huge prompts | Long RAG context increases time-to-first-token |
| Streaming off | Client waits for full completion |
| Sequential agent loops | Five Flash calls can feel slower than one Pro call |
Routing pattern: classify with gemini-3-flash → answer with gemini-3.5-flash → escalate failures to gemini-3.1-pro-preview.
See also: route GPT, Claude and Gemini for speed and Gemini API cost guide.
Decision matrix (production)
| Workload | Start with | Escalate when |
|---|---|---|
| Intent routing / tags | gemini-3-flash | Accuracy < target on golden set |
| Customer chat | gemini-3.5-flash | Quality complaints on evals |
| Coding copilot | gemini-3.5-flash | Hard bugs fail twice |
| Legal / 500K+ token RAG | gemini-3.1-pro-preview | — |
| Offline batch (non-urgent) | Google Batch API if eligible | Real-time UX required |
Python: switch Gemini model id (OpenAI-compatible)
import os
from openai import OpenAI
client = OpenAI(
api_key=os.environ["LUMEAPI_KEY"],
base_url="https://api.lumeapi.site/v1",
)
MODEL_BY_TASK = {
"route": "gemini-3-flash",
"chat": "gemini-3.5-flash",
"hard": "gemini-3.1-pro-preview",
}
def complete(task: str, messages: list) -> str:
model = MODEL_BY_TASK[task]
r = client.chat.completions.create(model=model, messages=messages)
return r.choices[0].message.contentLog model on every request. Your Usage export should match this table.
Monthly scenario (mixed Gemini stack)
Illustrative single-wallet workload on LumeAPI catalog rates:
| Surface | Model | Volume | ~Monthly cost |
|---|---|---|---|
| Classifier | 3 Flash | 400M in / 40M out | ~$192 |
| Chat | 3.5 Flash | 80M in / 25M out | ~$207 |
| Hard queue | 3.1 Pro | 15M in / 4M out | ~$47 |
| Total | ~$446 |
Same traffic on Pro-only defaults would cost several times more.
FAQ
Is Gemini 3.5 Pro the same as 3.1 Pro?
Google's lineup changes frequently. This guide compares 3.5 Flash vs 3.1 Pro Preview — the ids LumeAPI documents today. Verify model catalog before budgeting.
Should I use Flash for coding agents?
Start with 3.5 Flash. Escalate individual steps to Pro when evals show repeated tool or reasoning failures.
Does LumeAPI support Google Batch or grounding?
LumeAPI focuses on real-time OpenAI-compatible Chat Completions. Google-native Batch, Search Grounding, and Live API features require Google's official APIs.
How does this relate to OpenAI or Claude?
One LumeAPI key can route GPT, Claude, and Gemini. See multi-model API in Python and LLM pricing comparison.
Next steps
- Run shadow traffic on
gemini-3.5-flashvs your current default. - Add an escalation path to
gemini-3.1-pro-previewfor failed eval cases only. - Compare catalog rates on cheap Gemini API.