Groq 429 rate limit: read the retry-after header and back off both RPM and TPM

TL;DR

Limits apply at the organization level and free tier is much lower than paid. When you exceed rate limits the API returns 429 Too Many Requests.

Fix

1. Limits apply at the organization level and free tier is much lower than paid. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Groq 429 rate limit feature.
• The symptom matches: read the retry-after header and back off both RPM and TPM.

When NOT to use

• Unrelated Groq 429 rate limit issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Groq 429 rate limit.

Variant phrasings

read the retry-after header and back off both RPM and TPM

Why it happens

Groq enforces requests-per-minute and tokens-per-minute simultaneously. Hitting either returns 429.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source: Groq enforces requests-per-minute and tokens-per-minute simultaneously. Hitting either returns 429.

Verified resolution: [Groq docs]: when you exceed rate limits the API returns 429 Too Many Requests. Only 429 responses include the retry-after header (seconds to wait); every response carries x-ratelimit headers showing remaining requests/tokens and reset times for both the request and token windows. Limits apply at the organization level and free tier is much lower than paid. Check your actual quotas at console.groq.com/settings/limits. Back off on retry-after, and queue or throttle client-side to stay under both RPM and TPM.

Source URL: https://github.com/anonimo432hz/omnibrain-ai-proxy-smart/blob/HEAD/docs/providers/groq.md