Every DEVSAIO API key can have its own monthly spending limit. When a key reaches its limit in a calendar month (UTC), further requests with that key are refused until the next month, while your other keys keep working.
Why it matters
- Bugs: a loop that calls the API 10,000 times stops at your limit.
- Leaks: a stolen key can only spend what the limit allows.
- Agents: a coding agent stuck in a loop can't drain your balance.
- Budgets: each project or client gets its own budget.
Recommended setup
| Key | Suggested limit |
|---|---|
| Local development | small (a few dollars) |
| Each production app | a bit above its normal monthly spend |
| Bots and cron jobs | always set, sized to expected volume |
| Coding agents (Claude Code, Cline) | your personal comfort level |
| Shared with a contractor | the agreed budget |
How to choose the number
- Run the app normally for a week.
- Check the key's spend in Usage Logs.
- Set the limit to roughly 4–5 weeks of that, plus headroom.
When a key hits its limit
Requests return an error. Make sure your app shows a friendly message, and that you get alerted. Raise the limit in the dashboard if the usage is legitimate.
Combine limits with the rest of the API key security checklist.
Claude, GPT, Gemini, DeepSeek, image and video models through one OpenAI- and Anthropic-compatible endpoint. Prepaid, pay only for what you use.