👮Access limitations
Method whitelist
Our PAYG access is based on an RPC method whitelist:
Method | Restrictions or Limitations |
| N/A |
|
|
| N/A |
| N/A |
| N/A |
| N/A |
|
|
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
| N/A |
Rate limits
In addition to the method whitelist, the following rate limiting is in place:
User starts out with 10,000 credits
Credits are reset 300 seconds after the first request
Single RPC requests costs 2 credits
Batch RPC requests costs 1 credit per message in batch
These limits are visible in the X-RateLimit-Limit
, X-RateLimit-Remaining
and X-RateLimit-Reset
headers.
For WebSockets, we also limit a maximum of 100 concurrent connections per API key, and 50 concurrent connections per IP address per API key.
If you surpass these limits your requests will be throttled.
The rate limits of our service is subject to change at any time without notice. For increased limits, please get in touch with us and we'd be happy to figure out a solution that works for everyone.
Last updated