Gemini API has no single “billing tier” field that answers every cost or outage question. A project has a billing plan (Prepay or Postpay), inherits a usage tier (Free or Tier 1–3) from its linked Cloud Billing account, and is then governed by several different caps and rate limits. An API key is only a credential; it is not the payer.
If a request has stopped, do not buy credits or create another key yet. Open the signed-in Google AI Studio project, identify its Cloud Billing account, and record the plan, tier, balance or status, spend cap, and active rate limit. The visible state—such as Set up Prepay, No credits, or 429 RESOURCE_EXHAUSTED—determines the safe next action.
The 60-second signed-in billing check
Use the same project for every step. Mixing a key from one project with the billing screen for another is the fastest way to misdiagnose the problem.
- Identify the project. In AI Studio’s API Keys or Projects page, find the project that owns the key used by the failing request. Do not record or expose the secret.
- Identify the linked billing account. Confirm whether that project is linked to a Cloud Billing account and note the account name or ID.
- Read the billing plan and status. In AI Studio Billing, record Prepay or Postpay and any action message:
Set up billing,Set up Prepay, orNo credits. - Read the usage tier. In Projects or Rate Limits, record Free, Tier 1, Tier 2, or Tier 3. Do not infer it from a payment receipt.
- Read the spend controls. Check the Prepay balance if applicable, the project spend cap if available, and the billing-account monthly cap.
- Read the active limit. In Rate Limits, check the model and project dimensions that apply to the actual request. Public quota examples are not a substitute for this signed-in value.
The audit line is:
API key → project → Cloud Billing account → plan → tier → balance/status → project cap → account cap → active limit
Change only the failed layer. A new key in the same project will not create a new quota pool or repair an empty account balance.
Who owns what: key, project, and billing account
Google’s current billing documentation defines the relationship this way:
- API key: authenticates a request and belongs to a project. It has no independent plan, tier, balance, or budget.
- Project: aggregates the usage of its keys and is the unit on which active rate limits are applied.
- Cloud Billing account: supplies payment history, the assigned billing plan, tier qualification, and the aggregate monthly cap inherited by linked projects.
One billing account can therefore stop several projects at once. If a Prepay balance reaches zero or an account-level cap is reached, every affected project and key linked to that account can stop together. Conversely, moving a project to another billing account changes the inherited plan, tier context, rate-limit eligibility, and account cap. Google says the configured project cap is preserved during a move, but accumulated project spend resets to zero for the new billing cycle.
Free and Tier 1–3 are usage tiers, not payment schedules
The current qualifications and billing-account monthly caps are:
| Usage tier | Current qualification | Current billing-account monthly cap |
|---|---|---|
| Free | Active project or free-trial context | Not applicable |
| Tier 1 | Link an active billing account | $250 |
| Tier 2 | $100 paid and at least 3 days since the first successful payment | $2,000 |
| Tier 3 | $1,000 paid and at least 30 days since the first successful payment | $20,000–$100,000 |
Tier 2 and Tier 3 qualification is evaluated from the linked billing account’s cumulative eligible spend across Google Cloud services and the age of its payment history—not only the Gemini charges from one project. Meeting the published requirements is normally sufficient, but Google reserves review discretion, and a quota-increase request is never guaranteed.
Tier 1 qualification also does not prove that paid requests can run. If the account is assigned to Prepay, setup must be complete and the balance must be positive. Free-to-Tier-1 changes are usually quick; later tier changes generally appear within about 10 minutes after the qualifying payment is confirmed. A cost graph can lag by up to 24 hours, so use the project status and transaction state before concluding that an upgrade failed.
Free remains a separate operating state with model- and region-specific availability. For current no-cost models and account-specific limits, use the Gemini API Free Tier guide instead of assuming that disabling billing recreates a particular old quota.
Prepay and Postpay answer “when do I pay?”
The plan does not replace the tier. It determines the charging cycle attached to the billing account.
| Plan | How payment works | Main interruption boundary | Current limitation |
|---|---|---|---|
| Prepay | Buy Gemini API credits before use; usage is deducted near real time | A $0 balance stops all Gemini API keys in every linked project | Credits can expire; billing processing can still permit limited overage |
| Postpay | Accumulate charges and pay at the billing cycle or assigned threshold | Payment failure, account status, or the tier’s account cap can stop service | Eligibility is account-specific; manual switching is currently disabled |
New users currently default toward Prepay, but migration and eligibility can produce a different assignment or a choice in the signed-in setup flow. Treat the AI Studio Billing page as the source of truth for the account in front of you.
For Prepay, Google currently documents a $10 minimum purchase and a $5,000 maximum purchase or balance. Credits expire after 12 months and are generally nonrefundable except through the documented refund path when an eligible account switches to Postpay. Auto-reload is optional, and a separate monthly auto-charge limit can constrain automatic reloads; manual purchases do not count toward that auto-charge limit.
Tier 3 criteria may make an account eligible for Postpay, but the current billing page says the manual switch is temporarily disabled. Do not build a migration plan around a button that is absent. When a switch is available and completed, it changes all projects linked to that billing account and cannot be reversed on the same account.
A single Cloud Billing account can also run two charging cycles at the same time: Prepay for Gemini API in AI Studio and Postpay for other Google Cloud services. That is why “Cloud Billing is active” does not prove that Gemini has spendable Prepay credit. It also explains why unpaid Cloud charges or an invalid payment method can suspend Gemini access even when a Prepay balance remains.
The current $300 Google Cloud welcome or free-trial credit does not cover Gemini API usage in AI Studio for newly opened accounts under the documented post-March-2026 boundary. Other promotional credits have their own eligibility rules; on Prepay, even an eligible promotion requires an active positive Prepay balance before it can be consumed.
Five spend controls that must not be collapsed
“Limit” can refer to controls with different owners, scopes, and enforcement behavior.
| Control | Scope and purpose | What happens at the boundary | Important caveat |
|---|---|---|---|
| Prepay balance | Billing account; funds Gemini API usage | At $0, all linked Gemini projects stop | No automatic fallback to Free; metering lag can create a negative balance |
| Project spend cap | One project; monthly cost control | The project is intended to pause at its cap | Experimental, limited availability, IAM-dependent, and subject to about 10 minutes of overshoot |
| Billing-account monthly cap | All linked projects with Gemini API enabled | All affected projects pause until the next cycle, normally the first of the month | The cap is determined by usage tier and aggregates project spend |
| Cloud Billing budget | Selected Cloud scope; monitoring and alerts | Sends notifications at configured thresholds | It is not a hard stop by itself and notifications can be delayed or duplicated |
| Spend-rate limit | Project; rolling 10-minute quota guardrail | Returns 429 RESOURCE_EXHAUSTED | It is not the monthly account cap or the Prepay balance |
Google’s current rate-limit documentation lists rolling 10-minute spend-rate limits of $10 for Tier 1 and $200 for Tier 2 and Tier 3. Other active limits include RPM, TPM, RPD, and model-specific dimensions. Published figures and capacity can change, so troubleshoot from the signed-in project rather than a cached table.
Model token rates are another separate contract. They vary by model, context band, cache, batch mode, tool, and media unit. Use the current Gemini API pricing guide for workload economics; an account cap is not a model price.
Diagnose an interruption from the visible state
| Visible state or error | Most likely layer | First safe action | Do not assume |
|---|---|---|---|
Set up billing | The project has no linked billing account | Link or create an eligible account for that project in AI Studio | The API key alone enables Paid |
Set up Prepay | An account is linked, but required Prepay is not configured | Complete Prepay setup in AI Studio | An “active” Cloud Billing account is enough |
No credits or Prepay $0 | Prepay payment account missing or balance depleted | Purchase or restore credits and wait for payment confirmation | The project automatically returns to Free |
429 RESOURCE_EXHAUSTED | RPM, TPM, RPD, spend-rate, or another quota | Read the active limit and request pattern; wait, reduce, or request an increase as appropriate | Buying credits necessarily fixes it |
| Positive Prepay balance, but service suspended | Cloud payment status, account cap, quota, or processing lag | Check past-due Cloud charges, payment method, account cap, and active limits | A positive balance guarantees access |
| Payment complete, tier unchanged | Payment or tier-processing delay | Confirm the transaction status and allow the documented update window | The cost graph is real time |
A 400 FAILED_PRECONDITION can mean that Free is unavailable in the request region and billing is required. A 403 PERMISSION_DENIED, 500, 503, or 504 has a different diagnostic path and should not be labeled a billing-tier failure without matching evidence. For 429 retry and quota work, follow the Gemini API rate-limits guide.
Safe actions for upgrading, controlling spend, or returning to Free
To start or upgrade Paid
Link only the intended project to the intended Cloud Billing account. If the setup flow assigns Prepay, fund the documented minimum and confirm a positive balance before sending production traffic. Record the first successful payment time; Tier 2 and Tier 3 timing begins from that payment. Then check the signed-in tier and active model limit instead of assuming that a receipt grants capacity.
To control spend
Set a project spend cap where the feature is available, but leave headroom for metering delay and long-running Batch or agent work. Add Cloud budget alerts for early warning, not shutdown. For Prepay, choose an auto-reload trigger and monthly auto-charge limit that match the service’s acceptable outage and spend risk. High-throughput systems still need application-side concurrency, output, and retry limits because none of these dashboards is a zero-latency kill switch.
To return a project to Free
Unlink or disable billing for that project. Confirm that it now shows Free and check the model’s current Free availability and project limits before resuming. A depleted Prepay balance does not perform this downgrade automatically.
Recheck these facts before changing production traffic
Billing rules are account-, region-, and time-sensitive. Before acting, verify the signed-in Billing, Projects, Spend, Usage, and Rate Limits pages; confirm the current available-regions list; and review the payment method, currency, tax, and organization policy shown for the actual account.
The durable rule is simple: the key identifies the project, the project links to the payer, and the payer supplies the plan, tier, and shared cap. Once those objects are separated, both upgrades and outages become much easier to diagnose without buying the wrong credit or changing the wrong project.
