RATE_LIMITED

What triggered it

Every endpoint in VibeCord has a per-account rate limit. When you exceed it, the server returns HTTP 429 with a Retry-After header (in seconds) telling you when you can try again.

Typical limits per account:

Endpoint family	Limit
Chat / generation	60/hr
Deploy	60/hr
Token operations	120/hr
Read-only API	10000/hr

Different from QUOTA_EXCEEDED

RATE_LIMITED resets every hour or minute. QUOTA_EXCEEDED is your monthly generation cap. Both exist; they limit different things.

What to try

1. Wait the Retry-After window. The error response tells you exactly how long. The browser will usually show this as “Retry after 42s” or similar.

2. Stop retry loops. If your tab is auto-retrying every 2 seconds, you’re feeding the limit. Refresh the page to drop any background fetches.

3. Slow your scripts. If you’re calling the API from a script (e.g. CI), add 1-second sleeps between calls — most limits are minute-based, not second-based, but bursts trip the protection.

4. Upgrade tier. Pro and Studio have 4-10× higher limits. If you’re consistently hitting 429s on a paid plan, you’ve outgrown it.

Open billing

How to read the headers

When you get a 429, the response includes:

Retry-After: 60
X-RateLimit-Limit: 30
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1746652800

• Retry-After — seconds until you can try again.
• X-RateLimit-Limit — your tier’s cap for this endpoint.
• X-RateLimit-Remaining — calls left in the current window.
• X-RateLimit-Reset — Unix timestamp when the window resets.

When to contact support

If you’re seeing RATE_LIMITED on a paid plan but you’re nowhere near the limits in the table above:

• Drop a screenshot of the error response in Discord — include the headers
• Or email support@vibecord.dev

This sometimes means a script you don’t remember is still running in another tab. We can tell you which IP and User-Agent triggered it.