Google shipped Gemini 3.7 Flash on August 13. Three weeks after 3.6 Flash. Half the introductory price. Better on every benchmark that matters for coding and agentic workloads. It hit HN #3 with 879 points and 446 comments — and the comment thread is a goldmine of engineers describing exactly the routing problem Trimio solves.
The benchmark deltas from 3.6 to 3.7 Flash:
And the price:
The introductory pricing runs through December 31, 2026, rising to $1.50/$7.50 in January 2027. That's four months of half-price routing for a model that's materially better than its predecessor on every dimension Trimio's LCR engine optimizes for.
Three weeks ago, an LCR rule routing coding tasks to Gemini 3.6 Flash at $1.50/$7.50 was already a strong savings play against frontier models at $5–$15/MTok. Today, that same rule routing to 3.7 Flash at $0.75/$3.75 doubles the savings while improving output quality.
The math: a customer running 10M input tokens/month of agentic coding workloads on a frontier model at $15/MTok pays $150K/month. Route those same calls to Gemini 3.7 Flash at $0.75/MTok: $7.5K/month. That's a $142.5K/month savings — $1.7M/year — on a model that scores higher on FrontierCode, DeepSWE, and AutomationBench than the 3.6 Flash you were already considering.
This is the LCR thesis in action: the routing decision is not static. New models arrive, prices drop, benchmarks shift. The gateway layer automates the re-evaluation so your routing table doesn't require a human to notice that Google just halved its Flash pricing.
The 446-comment HN thread is unusually candid about Google's API friction. Selected quotes:
"I don't know what situation I'd reach for 3.7 Flash first for. Google really needs a differentiator, especially given how hard it is to get an API key from them. They can't be high friction and non-pareto."
"It's honestly been easier to use Anthropic to help me build my own search index than deal with Google."
"It was easier to go through OpenRouter than spend more energy on [the Gemini API]."
Engineers are not saying the model is bad. They're saying the access layer is painful. Google's onboarding — Cloud project setup, API key management, IAM configuration per team — is friction that costs engineering time. The model is worth routing to; the provider experience is not.
This is exactly the problem Trimio's virtual key layer solves. One Trimio key covers Google, Anthropic, OpenAI, and every other provider. No per-provider API key management. No Google Cloud project IAM per team. The friction that HN commenters are describing disappears for any team routing through Trimio.
On the same day Gemini 3.7 Flash shipped, Trimio merged support for x-goog-api-key as a virtual-key carrier header. Google Cloud services use x-goog-api-key as their native authentication format — not Authorization: Bearer. Enterprise teams that have standardized on Google's auth pattern can now adopt Trimio by changing their API endpoint (base_url) without touching their authentication code.
The combination: a better, cheaper Gemini model launches, and simultaneously Trimio removes the friction of routing to it through a Google-native auth flow. A Google Cloud team that was previously managing Gemini API access per-team through Google Cloud IAM can swap their base_url to Trimio, get LCR routing across all providers, and keep their existing x-goog-api-key auth pattern intact.
The AutomationBench delta deserves attention. Most coding benchmarks measure single-shot code generation. AutomationBench measures multi-step workflow execution — the kind of agentic loop where a model calls tools, reads results, decides next steps, and chains outputs across multiple turns. This is the workload pattern that dominates enterprise AI spend in 2026: not "write me a function" but "execute this business process."
A model that improves +13.4 points on workflow automation at half the price of its predecessor is a material event for any team routing agentic traffic. If your LCR rules were previously routing workflow tasks to a frontier model at 10× the cost, 3.7 Flash is the new default — and the routing decision should be automated, not manual.
The Gemini 3.7 Flash release also carries a subtext worth noting. The DeepMind departures in early August (Jeff Dean, Vinyals, Le, Ghemawat) cast doubt on Google's ability to iterate. A materially better, cheaper Flash model three weeks later is Google's remaining team shipping proof that the roadmap continues. For multi-provider routing, this matters: Google remains a viable routing target, but the talent concentration risk argument for any single-provider dependency still stands.
x-goog-api-key auth through Trimio — no auth refactor required.google/gemini-3.7-flash to your model routing table. Introductory pricing: $0.75/M input, $3.75/M output through December 31, 2026. Verify at ai.google.dev pricing.google/gemini-3.6-flash. At half the price with better benchmarks on every dimension, 3.7 Flash is the routing default for coding and agentic workloads. 3.6 Flash remains available as a fallback.Google halving Gemini Flash's price while improving every benchmark is a routing event. The teams that capture the savings are the ones whose gateway automates the model_rates update and LCR rule re-evaluation. The teams that don't will read about the price drop on HN, think "that's interesting," and keep paying 3.6 Flash rates until someone in finance notices three months later.
Trimio's LCR engine exists to make that update automatic. New model arrives, price drops, benchmarks improve — the routing table updates, the savings flow, no human intervention required. That's the thesis. Gemini 3.7 Flash is the proof.
Trimio is the LLM API gateway with least-cost routing that automatically incorporates new models and price changes. See how it works.