Credits¶
Every MCP tool call costs credits. Credits are tracked per API key with rolling quotas.
How Credits Work¶
Each tool has a fixed credit cost that is deducted from your quota when the tool is called. Bulk tools charge per item rather than per call – for example, parsing 10 User-Agent strings in a single bulk call costs 10 credits (1 per UA), not 2 as a single parse would.
Quotas are tracked via Redis with a rolling time window. When your quota resets, your full credit allowance is restored automatically. There is nothing to top up or configure – the system manages it based on your plan tier.
Credit Costs¶
Tool |
Credits |
|---|---|
|
2 |
|
1 / UA |
|
5 |
|
1 |
|
3 |
|
1 / code |
|
2 |
|
1 |
|
3 |
|
2 |
|
2 |
|
2 / code |
|
5 |
|
1 |
|
1 |
|
1 |
|
2 |
|
1 |
|
3 |
|
4 |
|
4 / email |
Quota Headers¶
Every response includes three headers that report your current quota status:
Header |
Description |
|---|---|
|
Total credits available in your current rolling window. |
|
Credits remaining before the next reset. |
|
Unix timestamp when your quota window resets and credits are restored. |
These headers are set on every successful response and on quota-exceeded errors, so your client always has visibility into usage.
Exceeding Your Quota¶
When your remaining credits reach zero, subsequent tool calls return an error with the quota limit and the reset timestamp:
Quota exceeded. Limit: 1000, resets at: 1711497600
Wait for the reset window or upgrade your plan tier for a higher allowance.
Note
The quota system is designed to fail open. If the Redis backend is temporarily unavailable, requests are allowed through rather than blocked. This ensures brief infrastructure issues do not disrupt your workflow.