【Conclusion】As of March 25, 2026, Gemini API now appears to support monthly spend caps inside Google AI Studio.
Until recently, the common understanding was: you could set alerts with Budgets, but you could not meaningfully set a hard monthly spending cap inside the Gemini API / AI Studio workflow itself. That was also the conclusion of my earlier article about whether Gemini API had a billing cap: Can You Set a Billing Cap on Gemini API Keys?
But when I opened AI Studio today, I found a new Monthly spend cap card and a Set spend cap dialog.
Google's official documentation already reflects this change. The Gemini API Billing page now has a Spend caps section, and its visible last updated date is 2026-03-23 UTC.
What changed
The change has two layers:
- Project spend caps
- Billing account tier spend caps
【Point】This is a real shift from the old "alerts only" situation. Gemini API billing controls are now explicitly moving toward monthly spending limits inside AI Studio.
1. Project-level spend caps
The official docs state that you can set your own project-level monthly spend caps from the AI Studio Spend page. Google currently labels this feature as Experimental.
The UI I saw also clearly showed a field for entering a monthly cost limit. This is especially useful if you run multiple projects under one billing account and want to allocate risk separately.
2. Billing account tier spend caps
There is also a billing-account-level monthly spend cap tied to your usage tier. These are preset, not freely configurable:
- Tier 1: $250
- Tier 2: $2,000
- Tier 3: $20,000 – $100,000+
According to the official docs, these tier spend caps will start being enforced on April 1, 2026, while the interface may appear earlier so users have time to adjust.
Where to set it
At the moment, the flow is inside Google AI Studio:
- Open Google AI Studio
- Select a paid project
- Open the Spend page
- Click Edit spend cap under Monthly spend cap
- Enter your amount and save
【Caution】This is still not per-API-key billing control. The official docs explicitly say API keys do not have independent billing settings; they inherit the project's and billing account's billing state and caps.
Important caveats
This is a major improvement, but it is still not a perfect "never exceed by even one cent" system.
- Batch mode completions may still incur overages
- Billing data can be delayed by up to around 10 minutes
- You need to understand both project caps and billing-account caps
- Spend is still aggregated across all keys within the same project
【Caution】The docs explicitly warn that you may still see small overages beyond the project cap because billing signals are not fully real time.
Why this matters
This is a big practical improvement for solo developers and small teams.
Before this, Gemini API had a real psychological barrier: it was easy to experiment with, but people worried that a bug, loop, or prompt mistake could create an unexpectedly large bill. Spend caps do not remove all risk, but they reduce it substantially.
- You can keep a low cap on test projects
- You can separate production and experimental usage
- It is much safer than relying on alerts alone
So yes, my earlier "you can't really cap it" conclusion needs updating in light of this new AI Studio and documentation change.
Summary
【Conclusion】Gemini API / Google AI Studio now has a real monthly spend-cap story, with both project-level controls and billing-account-level limits.
What I confirmed today:
- AI Studio now shows a Monthly spend cap UI
- Official billing docs now include a Spend caps section
- Project spend caps are marked Experimental
- Billing-account tier caps are scheduled for enforcement on April 1, 2026
- Small overages are still possible because of processing delays and batch mode
For anyone who avoided Gemini API because cost control felt too weak, this is a meaningful change.
References:
- Gemini API Billing https://ai.google.dev/gemini-api/docs/billing
- Gemini API Rate limits https://ai.google.dev/gemini-api/docs/rate-limits
