Limits and quotas
Limits keep the service fast and protect your credits if a key leaks.
Limits per package
| Limit | Credit | Starter | Pro |
|---|---|---|---|
| Requests per minute, per key | 60 | 60 | 120 |
| Requests per minute, per account | 60 | 120 | 300 |
| Writes per minute, per key | - | - | 30 |
| Tool runs per minute, per key | 6 | 6 | 10 |
| Tool runs per hour | 30 | 30 | 60 |
| Tool runs per day | 100 | 100 | 300 |
| Tool runs at the same time | 2 | 2 | 3 |
| Requests per month, API and MCP together | 1.000 | 1.000 | 10.000 |
| Credits per day, per key, default | 50 | 50 | 200 |
Headers
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Your limit for this window |
X-RateLimit-Remaining | What is left |
X-RateLimit-Reset | When it resets, Unix time |
Retry-After | Seconds to wait after a 429 |
MessGEO-RateLimit-Scope | Which limit was reached |
Monthly quota
At 100 percent requests keep working and the header MessGEO-Quota: exceeded appears. At 120 percent requests return 429 monthly_quota until the next month. Errors and dry_run calls do not count.
Daily credit cap
Every key that can run tools has a daily credit cap, which you can change in the panel. The account has a separate total of 500 credits per day. A run that would pass a cap returns 402 daily_credit_cap.