Requests included per plan
- The quota covers a calendar month (UTC) and resets on the 1st at 00:00 UTC. Unused requests do not roll over.
- The RPC plan is RPC only: its keys are refused by the Data API (REST and WebSocket) and it includes no API credits. Top up credits to keep going past 15M requests in a month.
- Calls per second count JSON-RPC calls, not HTTP requests: a batch of 20 counts as 20.
- The RPC rate is separate from the REST rate: a busy RPC client does not slow the Data API on the same account.
eth_getLogswithblockHashis always one block. Ranges above your plan’s limit are refused with-32005; split them.
How requests are counted
- A batch counts the sum of its calls.
- WebSocket notifications count 1 request each (one
newHeadsevent, onelogsevent). - Refused calls are not counted: missing or invalid key, rate limit, blocked method, range or batch over the limit.
- Calls the node answers with an error (
execution reverted…) are counted: the node did the work.
eth_chainId + eth_call + eth_getLogs counts 0 + 1 + 3 = 4 requests. The response says so in X-RPC-Requests: 4.
Past the quota
- Each further block of 100 requests uses 1 API credit from the account’s balance (the same balance as the Data API).
- When the quota is used up and the credit balance is empty, calls are refused with HTTP
402(code-32005) and WebSocket connections close with code4402. Top up or upgrade in the console.
Response headers
The console shows the month’s usage by chain and method under RPC.
Caching
Responses that can no longer change are cached at the edge: blocks, transactions, receipts and logs designated by hash, or by an explicit block number below the chain head, and calls made at such a block. A cached response carriesX-Cache: HIT and is faster; it counts the same requests.