Unverified50% confidenceFactExact time
For the same HTTP 429 status code, the Gemini API returns three semantically different quota-exhaustion cases: limit 0 means the current tier has no quota at all for that model; limit 5 (per minute) means the per-minute request count is exhausted; limit 20 (per day) means the daily request count is exhausted.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/16/2026
First Seen
Valid until: 1/14/2027
Sources
Related Entities
Related Claims
UnverifiedA Gemini API 429 error only tells the caller that resources are insufficient, but does not say which type of resource is lacking; the correct way to handle a 429 is to parse the details array to distinguish complete lack of quota, per-minute overage and daily overage.78% similarUnverifiedThe Gemini API free tier has a quota of 0 for Pro-series models such as gemini-3.1-pro-preview, returning limit: 0, and it remains 0 after the daily reset, so waiting to retry is pointless.75% similarUnverifiedIn the Gemini API's continuation protocol, a single streaming request is capped at 65,536 tokens, while a non-streaming direct HTTP request is 32,768.72% similarUnverifiedThe Gemini API returns 429 RESOURCE_EXHAUSTED, indicating the violated window in details[].quotaId and giving a retryDelay for per-minute limits, with its daily quota resetting at midnight Pacific Time.71% similarUnverifiedIf the max_output_tokens limit is set too low, Gemini 4 Argon returns an empty answer but still bills as usual.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1045854API
curl https://kongchang.com/api/v1/knowledge/claims/1045854MCP
get_claim(id=1045854)