> For the complete documentation index, see [llms.txt](https://docs.apismart.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apismart.ai/troubleshooting/balance-and-usage-limit-issues.md). # Balance and Usage Limit Issues Troubleshoot insufficient balance, usage limits, rate limits, unexpected costs, and related ApiSmart API errors. ApiSmart requests may fail when your account does not have sufficient balance or when request activity reaches a service limit. Use the HTTP status code and error code to identify the cause before retrying. ### 💳 402 — Insufficient Balance If the API returns: ``` 402 insufficient_quota ``` your account does not have sufficient available balance to complete the request. Before retrying: 1. Check your current wallet balance. 2. Review recent API costs in [**Usage Logs and Costs**](/api-usage/usage-logs-and-costs.md). 3. Confirm that recent funding or payments were completed successfully. 4. Add funds if necessary. 5. Retry the request after sufficient balance becomes available. Adding funds does not automatically retry a previously failed API request. ### 📊 Check Recent Usage If your balance is lower than expected, open: **Console → Usage Logs**
Review: * API Key Name * Model * Billing Mode * Consumption * Cost * Status * Request ID Different model types use different billing methods, so **Consumption** does not always mean text tokens. For example, costs may depend on: * Text token usage * Number of generated images * Video duration * Video generation tokens * Resolution * Model-specific parameters For billing rules, see **Model Pricing and Billing**. ### 🔍 Unexpected Balance Changes If your balance changed more than expected: 1. Check **Usage Logs** for high-cost requests. 2. Filter by **API Key**, **Model**, and **Billing Mode**. 3. Look for repeated or duplicate requests. 4. Review image or video requests that may generate multiple outputs. 5. Compare the request with the pricing rules for the selected model. For account payments and recharge records, see [**View Your Balance and Transaction Records**](/account-and-wallet/view-your-balance-and-transaction-records.md). ### ⚠️ 429 — Rate Limit Exceeded If the API returns: ``` 429 rate_limit_error ``` the request has reached a service rate limit. This is different from insufficient balance. Do not immediately send repeated retries. Instead: * Reduce request frequency * Add a delay between requests * Use exponential backoff * Limit the number of automatic retry attempts For example: ``` 1 second → 2 seconds → 4 seconds → 8 seconds ``` A `429` response does **not** mean that you need to add funds. ### 🧩 Balance vs. Rate Limit | Error | Meaning | Recommended Action | | ------------------------ | ------------------------------ | --------------------------- | | `402 insufficient_quota` | Insufficient available balance | Check balance and add funds | | `429 rate_limit_error` | Request rate limit reached | Slow down and retry later | Checking the status code first is usually the fastest way to determine which issue you are experiencing. ### 🎬 Check High-Cost Media Requests Image and video requests can have different cost behavior from text generation. When troubleshooting unexpected usage, check: * Selected model * Number of generated images * Sequential image generation settings * Video duration * Video resolution * Whether a request was repeated For video models in particular, parameters such as duration and resolution can affect billing, so avoid relying on defaults when the API guide recommends explicit values. See [**Image Generation API**](/api-guides/image-generation-api.md), [**Video Generation API**](/api-guides/video-generation-api.md), and [**Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md) for details. ### 🔎 If a Cost Looks Incorrect Find the corresponding request in [**Usage Logs and Costs**](/api-usage/usage-logs-and-costs.md) and record its: * Request ID * Request time * Model * Billing Mode * Consumption * Cost * Status If the charge still cannot be explained, contact [**ApiSmart Support**](/help-and-resources/contact-support.md) and provide the relevant Request ID. Never provide your full API Key to support. ### ✅ Quick Troubleshooting Checklist If a request fails because of balance or usage limits: * Check whether the status is `402` or `429` * Review your available wallet balance * Check recent Usage Logs * Confirm the selected model and billing method * Look for duplicate or repeated requests * Review image or video parameters that affect cost * Use controlled backoff for `429` * Add funds before retrying a `402` request For other API failures, see [**HTTP Status Codes and API Errors**](/troubleshooting/http-status-codes-and-api-errors.md). ### ➡️ Next Steps * [**Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md) * [**Usage Logs and Costs**](/api-usage/usage-logs-and-costs.md) * [**View Your Balance and Transaction Records**](/account-and-wallet/view-your-balance-and-transaction-records.md) * [**Add Funds and Understand Wallet Credits**](/account-and-wallet/add-funds-and-understand-wallet-credits.md) * [**HTTP Status Codes and API Errors**](/troubleshooting/http-status-codes-and-api-errors.md)