# Access limitations ## Method whitelist Our PAYG access is based on an RPC method whitelist:

Method	Restrictions or Limitations
Method	Restrictions or Limitations
`eth_getTransactionCount`	N/A
`eth_subscribe`	Number of subscriptions may be limited
`eth_unsubscribe`	N/A
`eth_getBalance`	N/A
`eth_getBlockByNumber`	N/A
`eth_call`	N/A
`eth_getLogs`	Maximum 10 calls per 30 minutes Must use a filter Filter must contain at least one topic Will only search the last 100 blocks at most.
`eth_sendRawTransaction`	N/A
`eth_getTransactionReceipt`	N/A
`eth_blockNumber`	N/A
`eth_chainId`	N/A
`eth_getCode`	N/A
`net_version`	N/A
`eth_getUncleByBlockHashAndIndex`	N/A
`eth_coinbase`	N/A
`eth_gasPrice`	N/A
`eth_estimateGas`	N/A
`eth_feeHistory`	N/A
`eth_protocolVersion`	N/A
`eth_getTransactionByHash`	N/A
`eth_getTransactionByBlockHashAndIndex`	N/A
`eth_getTransactionByBlockNumberAndIndex`	N/A
`eth_getUncleByBlockNumberAndIndex`	N/A
`eth_getBlockByHash`	N/A
`eth_getStorageAt`	N/A
`eth_syncing`	N/A
`eth_mining`	N/A
`eth_protocolVersion`	N/A
`eth_getBlockTransactionCountByNumber`	N/A
`eth_getUncleCountByBlockNumber`	N/A
`eth_getBlockTransactionCountByHash`	N/A
`eth_getUncleCountByBlockHash`	N/A
`web3_clientVersion`	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.