429Too Many Requests / Rate limit
Request frequency, token usage, or concurrency exceeds the current plan limit.
Wait for recovery, reduce concurrency and context, or check the official usage dashboard.
Distinguish official rate limits, insufficient balance, permission issues, and provider incidents. Always manage accounts and billing through official channels.
Request frequency, token usage, or concurrency exceeds the current plan limit.
Wait for recovery, reduce concurrency and context, or check the official usage dashboard.
The balance is insufficient, plan quota is exhausted, or billing does not cover the model.
Review billing and usage; recharge or upgrade only through official channels.
Model permission, region, organization policy, or API key scope is insufficient.
Check key scopes, organization policy, and model access.
An upstream model or aggregation platform returned a quota error.
Inspect provider attribution, switch to an officially recommended model, or retry later.
Upstream capacity is low and may relate to provider load or an incident.
Check the provider status page; do not infer a personal quota reset.