Usage and rate limits
Identify whether a refusal comes from credits, a rolling usage window, concurrency, an API ceiling, or your own provider before changing plans.

- Read the complete error and preserve its request or task identifier.
- Open Account → Usage and check monthly credits plus the weekly window.
- For API
429responses, respectRetry-Afteror the rate-limit reset header and reduce concurrency. - For BYOK failures, inspect the provider account’s quota and billing rather than Foxora credits.
- Retry one small request after the indicated window or configuration change.
Do not repeatedly retry an unchanged request: that can extend congestion and make diagnosis harder. Upgrade only after confirming the blocked resource is included in the target plan.
Expected result: one controlled retry succeeds, or the same response clearly names the remaining limit and recovery time.