> 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
API requests may fail when your account balance is insufficient, usage limits are reached, or the selected model requires more available credit.
Before troubleshooting, confirm your **Current Balance**, API Token usage status, and recent request records.
For detailed billing information, see [**Understand Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md).
***
### Check Your Current Balance
Before sending paid API requests, confirm that your wallet has sufficient balance.
Check:
* Current Balance
* Recent top-up records
* Recent API usage
* Selected model cost
You can review your balance in:
```
Console β Wallet
```
For balance history and payment records, see:
[**View Your Balance and Transaction Records**](/account-and-wallet/view-your-balance-and-transaction-records.md)
***
### Common Balance Errors
#### Insufficient Balance
An insufficient balance error usually means the wallet does not have enough available credit for the request.
Check:
1. Current Balance
2. Selected model pricing
3. Request size or generation settings
4. Recent API usage
Possible causes:
* High-cost models
* Large input requests
* Image generation requests
* Video generation requests
* Multiple applications using the same wallet balance
***
#### Balance Is Available but Request Still Fails
If your wallet has balance but requests still fail, check:
* Whether the correct API Token is being used
* Whether the Token has reached its usage limit
* Whether the selected model requires additional access
* Whether the request itself is valid
A successful wallet top-up does not guarantee every API request will succeed.
The request must also pass:
* Authentication checks
* Model validation
* Request validation
* Usage restrictions
***
### API Token Usage Limits
API usage may also be affected by Token-level limits.
Check:
* API Token status
* Token usage allowance
* Whether the Token has been disabled
* Whether your application is using multiple Tokens
If multiple API Tokens belong to the same account, usage may be deducted from the same wallet balance.
For Token management, see:
[**Create and Manage API Tokens**](/api-tokens/create-and-manage-api-tokens.md)
***
### Unexpected Balance Changes
If your balance changes unexpectedly, check:
#### 1. Recent API Requests
Open:
```
Console β Usage Logs
```
Review:
* Request time
* Model
* Consumption
* Cost
* Token Name
***
#### 2. Running Applications
Unexpected usage may come from:
* Background services
* Automated scripts
* Scheduled tasks
* Multiple environments using the same API Token
Check all applications that use your API Token.
***
#### 3. High-Cost Models
Different models may have different billing methods.
Examples:
| Model Type | Possible Billing Factors |
| ------------ | ------------------------------- |
| Text Models | Input/output usage |
| Image Models | Generated images and settings |
| Video Models | Generated duration and settings |
Always check the selected modelβs pricing before running large workloads.
***
### Top-Up Completed but Balance Did Not Update
If a payment was completed but your balance has not changed:
1. Refresh the Wallet page.
2. Check **My Orders**.
3. Confirm you are signed in to the correct account.
4. Verify the payment status.
5. Wait for processing to complete.
Do not submit the same payment again immediately.
For payment-related issues, see:
[**View Your Balance and Transaction Records**](/account-and-wallet/view-your-balance-and-transaction-records.md)
***
### Check Usage Logs
When investigating unexpected charges or failed requests:
1. Open **Usage Logs**.
2. Find the related request.
3. Review:
* Request ID
* Model
* Token Name
* Consumption
* Cost
* Status
* Error Message
Usage Logs provide the most accurate record of API consumption.
***
### When to Contact Support
Contact support if:
* Balance does not update after a completed payment.
* A request fails despite sufficient balance.
* Usage records appear incorrect.
* Charges cannot be explained through Usage Logs.
Include:
* Request ID
* Order ID (if payment-related)
* Account email
* Request time
* Model ID
* Error message
* Relevant screenshots
Do not include:
* Full API Token
* Account password
* Payment credentials
> π Never provide your full API Token to support.
***
### π Next Steps
Continue with:
* [**View Your Balance and Transaction Records**](/account-and-wallet/view-your-balance-and-transaction-records.md)
* [**Understand Model Pricing and Billing**](/models-and-pricing/model-pricing-and-billing.md)
* [**Usage Logs and Costs**](/api-usage/usage-logs-and-costs.md)
* [**API Token and Authentication Issues**](/troubleshooting/api-token-and-authentication-issues.md)
* [**HTTP Status Codes and API Errors**](/troubleshooting/http-status-codes-and-api-errors.md)