How do I fix 429 rate_limited?

429 rate_limited is about speed, not money: the key exceeded its requests per minute (10, 30, 60 or 120).

1. Read Retry-After and wait that many seconds.
2. Retry with backoff, never in a tight loop.
3. Watch X-RateLimit-Remaining and slow down near zero.
4. Stream run events instead of polling.
5. If it's steady traffic, create a key with a higher limit.

This isn't your plan limit; those use window_limit_reached, weekly_limit_reached or monthly_limit_reached.

Good to know#

• Branch your code on the error code, not the message.
• Every API request sends your key and your Account ID (X-Clatter-Account: CL-…); a key alone is refused.
• A new key's secret is shown only once. Clatter Labs stores only a hash, so a lost key can't be recovered.

Learn more#

• Errors guide
• API errors reference
• Model API errors

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.