What does 429 rate_limited mean on the Model API?
Your key sent more requests in a minute than its limit (10, 30, 60 or 120 requests per minute, chosen when the key was made).
Code: rate_limited · HTTP status: 429
The limit is per key, not per account. The response carries Retry-After with the seconds to wait.
Common causes#
- a burst of parallel requests
- a retry loop without waiting
- several services sharing one key
How to fix it#
- Wait the
Retry-Afterseconds, then retry. - Watch
X-RateLimit-Remainingand slow down before it hits zero. - Give each service its own key, or create a key with a higher limit.
Should my code retry?#
Retryable after Retry-After. Don't retry in a tight loop.
The error body uses the OpenAI shape, so OpenAI SDKs raise it as an exception you can catch:
{"error": {"message": "...", "type": "...", "code": "rate_limited", "param": null}}
Every response also carries an X-Request-Id. Keep it in your logs; it's the quickest way for support to find a request.
See the full list in the Model API reference.
Still need help?#
- General support: support@clatterlabs.com or team@clatterlabs.xyz
- Infrastructure questions, or permanent deletion of your data (your whole account or one service): infrastructure@clatterlabs.xyz
We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.