RATE_LIMITED
Free plan: this month's credits are used up. They reset at the start of the next UTC month.
Wait for reset
What this means
[02]RATE_LIMITED means your monthly plan credits are used up and your plan can't spill into bought credits. Only Free gets it. Paid plans move on to bought credits instead, and get PAYMENT_REQUIRED when those run out too. The limit is monthly, not daily. The body's `retry_after` field is an ISO date: the end of the current UTC month, when credits reset.
When you'll see it
[03]HTTP 429. Body always includes code: "RATE_LIMITED". Branch on code, never on the human-readable message — wording can change without notice; the code is the stable contract.
Example response
[04]{
"status": "error",
"code": "RATE_LIMITED",
"message": "Monthly quota exceeded",
"retry_after": "2026-10-01T00:00:00.000Z"
}How to handle
[05]Wait for the reset or upgrade to a paid plan. Free can't buy credits. In automated jobs, read `retry_after` and pause until then. In apps, show a clear "monthly limit reached" message. Don't loop-retry; you'll get the same 429.
Suggested handling in a Node client:
if (data.code === 'RATE_LIMITED') {
// Monthly credits used up. Don't retry — wait for the reset or upgrade.
const resetMs = new Date(data.retry_after).getTime() - Date.now();
notifyOps(`Onto credits reset in ${Math.round(resetMs / 1000 / 60 / 60)}h`);
throw new Error(data.message);
}A paid plan used up its monthly credits and has no bought credits left.
Too many requests running at once for your plan. Wait a second and retry.
See the full error index for the complete catalog with the handling switch statement covering every code at once.