Usage and limits
MCP usage and limits
Every tool call is an API request made with your key. Each call counts against your plan allowance and against a separate, smaller daily allowance for MCP calls. This prevents a single agent conversation from consuming your entire daily allowance.
What counts
Only tool calls reach the API.
- Each tool call counts as one API request against your plan quota and per-minute rate limit, and as one call against your daily MCP allowance.
- A workflow makes several requests in one call, and each request counts. The page for each workflow states the maximum number of requests it can make. Workflows reduce the number of assistant turns and tokens, not the number of requests.
- A call is refused as soon as you reach any one of these limits. When the MCP allowance is used up, the same key continues to work when you call the API directly.
- Connecting to the server and listing tools do not call the API and are not counted.
- A call that the API refuses because of your plan or allowance still counts, in the same way as a refused direct request. A call made with a key that the API does not recognise is not counted.
- A single question can require several tool calls, for example one call to resolve a name and another to read the record.
Limits by plan
These figures come from the plan configuration that the API enforces. The MCP allowance is part of the daily cap, not an addition to it. Tools above your plan still appear in the tool list, but calls to them are refused.
| Plan | Requests per month | Per minute | Daily cap | MCP calls per day | Tools you can call |
|---|---|---|---|---|---|
| Explorer | 200 | 10 | 50 | 20 | 19 of 35 |
| Builder | 25,000 | 60 | 2,000 | 500 | 29 of 35 |
| Studio | 150,000 | 120 | 10,000 | 2,500 | All 35 |
| Enterprise | 1,000,000 | 300 | 50,000 | 10,000 | All 35 |
Full plan details, pricing and the per-endpoint access matrix are available on Plans and limits.