How should my code handle 429 and 402 billing errors?
| Code | Do |
|---|---|
rate_limited | Wait Retry-After seconds, retry with backoff |
too_many_runs | Wait for a run to finish or cancel one |
window_ / weekly_ / monthly_limit_reached | Wait until resets_at |
team_daily_quota_reached / team_spend_limit_reached | Wait until resets_at; tell the owner |
out_of_credits (402) | Stop, alert someone, add credits — retrying won't help |
account_suspended (403) | Don't retry before resets_at |
Never retry billing errors in a tight loop.
Good to know#
- Plans and credits are sold through Gumroad, the merchant of record, which also handles receipts and taxes.
- New accounts get $5 of free credit once for the Model API and Agent API.
- Questions about a charge or usage figure should be raised within 60 days.
Learn more#
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.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.