Vaelor limits throughput with credits rather than fixed requests-per-minute quotas. As long as your balance covers a request, it runs. A few endpoints add concurrency limits to protect long-running work.
Credit-based throughput#
Your plan's credits refresh every 12 hours. A Plus plan, for example, can spend 300 credits per window — roughly 300 short medium chat replies, 15 Flash images, or a five-minute song. When the balance runs out, requests fail with 402 until the next refresh or until you add permanent credits.
Concurrency limits#
| Resource | Limit | When exceeded |
|---|---|---|
| OSINT runs | 1 active run per account | 409 |
| Music tracks | 1 render per requestId | 409 DUPLICATE_REQUEST |
| API keys | 10 per account | 409 KEY_LIMIT_REACHED |
Size limits#
| Limit | Value |
|---|---|
| Chat input | 100,000 characters |
| Chat attachments | 10 per request |
| Image prompt | 2,000 characters |
| File upload | 20 MiB per file |
| OSINT case files | 50 files, 200 MiB total |
| OSINT material | 50,000 characters |
Fair use#
We may temporarily slow or block traffic that degrades the service for others, such as large bursts of parallel requests from a single key. If you're planning sustained high-volume use, contact us first and we'll make sure your account is ready for it.