Unverified50% confidenceDecision RuleExact time
A 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFor 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.78% similarUnverifiedThe 503 UNAVAILABLE returned by the Gemini API indicates server-side overload and is unrelated to the user's quota; there is no retry delay in the error, so exponential backoff with jitter should be used to retry.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.70% similarUnverifiedGemini's free tier has limitations on call frequency, and summaries occasionally miss key details68% similarUnverifiedWhen Gemini's quota is exhausted it throws a gRPC-style RESOURCE_EXHAUSTED error wrapped in an HTTP 429 response, rather than returning a custom header suite.67% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1045886API
curl https://kongchang.com/api/v1/knowledge/claims/1045886MCP
get_claim(id=1045886)