# 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.

![Usage and rate limits](https://www.foxora.ai/docs/images/v5.0.8/reference/settings-usage.webp)

*Studio interface in English. Sample data.*

1. Read the complete error and preserve its request or task identifier.
2. Open **Account → Usage** and check monthly credits plus the weekly window.
3. For API `429` responses, respect `Retry-After` or the rate-limit reset header and reduce concurrency.
4. For BYOK failures, inspect the provider account’s quota and billing rather than Foxora credits.
5. 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.