AI provider balance
The check monitors AI provider balance and warns before the money runs out. Out of money looks like your service is broken: requests stop working, though network and the model itself are fine.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check. | Specify whose account you're controlling. | DeepSeek balance |
| Group | Allows assigning task to project or section. | Select a group if you want to keep project tasks together. | Main project |
| Provider | Service whose balance is requested. | Choose provider whose key you use. Only those in the list provide balance with regular key. | DeepSeek |
| API key | Key for making the balance request. | Paste key from provider's account. When updating task, leave field empty to keep previous key. | sk-… |
| Timeout | How long to wait for provider response. | Didn't respond in time — check is skipped, not reported as problem: provider delay says nothing about your money. | 30 seconds |
| Minimum balance | Threshold below which task reports problem. | Specify reserve enough for account top-up. Threshold is set in provider's account units. | 5 |
| Interval | How often to check balance. | An hour is enough even at fast spending: balance changes slower than availability. | 1 hour |
| Notification channels | Where to send messages about issue and recovery. | Check channels where you actually read notifications. | Telegram and email |
| Reports | Periodic summaries for the task. | Enable if you want overview without manual panel access. | Weekly report |
When alert comes
Alert comes when balance drops to specified threshold or below. Alert also includes provider refusal to name balance for reason concerning you: for example, key revoked or funds already out.
When check is skipped
If balance not named for reason unrelated to your money, task doesn't fail or recover — check is simply skipped, task status stays the same. This happens when:
- couldn't reach provider or it didn't respond in time;
- provider has outage and responds with server error;
- provider asked to check less often;
- OpenRouter key has no spending limit assigned, has no balance.
Notification settings
For each notification channel in a task additional parameters can be set. They apply only to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or disables sending notifications via this channel for this task. |
| Delay for PRO | Delays first DOWN notification for selected time (up to 12 hours). Convenient to avoid alerts for short-term failures. |
| Repeat every PRO | Periodically repeats notification while task stays in DOWN status (up to 1 hour between repeats). Suitable when important not to miss prolonged failure. |