Tools API — Usage Limits
Current tools-API usage limits by plan. Numbers are live from the plan catalog and reflect any operator adjustments.
| Plan | Monthly | Yearly | Tools calls | Storage requests | Bandwidth | Rate tier | Overage |
|---|---|---|---|---|---|---|---|
| Free | Free | — | 100 / tool / month | 1M | 25 GB | low |
— |
| Hobby | $5.00 | $50.00 | 1k / tool / month | 10M | 250 GB | mid |
Call: $0.02 BW: $0.50 / GB |
| Starter | $10.00 | $100.00 | 2k / tool / month | 20M | 500 GB | high |
Call: $0.02 BW: $0.50 / GB |
| Pro | $30.00 | $300.00 | 6k / tool / month | 60M | 1,500 GB | unlimited |
Call: $0.02 BW: $0.50 / GB |
Rate tiers
Burst limits applied in addition to the monthly allotment. Independent of plan quota — both must pass for a request to proceed.
| Tier | Per minute | Per hour | Per day |
|---|---|---|---|
low | 30 | 600 | 5k |
mid | 120 | 3k | 30k |
high | 300 | 10k | 100k |
unlimited | 1k | 50k | 1M |
When you exceed a limit
- Plan allotment exhausted, wallet has credit: the request proceeds and the per-call overage rate is debited from your wallet.
- Plan allotment exhausted, wallet empty (or plan is Free): the request is rejected with HTTP 402 (wallet insufficient) or 429 (plan limit), with
planLimitandupgradeUrlin the response body. - Burst rate exceeded: HTTP 429 with
Retry-Afterheader. This applies before the monthly allotment check.
Operational Metrics
The platform records raw cpu_ms, normalized compute units, and average per-request CPU utilization signals for usage analysis.
These appear in /usage, project Usage & Quotas, and admin usage screens.
They are observability metrics today, not plan enforcement limits.
Need higher limits? Check the plans page or request a dedicated VPS.