RPC Support
Our partner Blockvision provides high-quality private RPCs at an affordable price. You can read more about it here: https://docs.blockvision.org/reference/rate-limits-and-compute-units
Rate Limits and Compute Units
The illustration of what Compute Units are and how we use them.
Compute Units are a measure of the total computing resources that your application uses on BlockVision. Some query interfaces are lightweight and fast (e.g. eth_blockNumber), while others can be more complex and require more resources(e.g. eth_call). Each method is assigned a certain number of computational units derived from the global average duration of each method.
Pricing Plans
Price | $0/Month | $29/Month | $99/Month | $199/Month |
Compute Unit | 10,000,000 | 100,000,000 | 600,000,000 | 1,500,000,000 |
EVM Approx. Request | 400,000 | 4,000,000 | 24,000,000 | 60,000,000 |
Compute Units / Second | 300 | 500 | 1,000 | 2,000 |
Max App | 5 | 6 | 10 | 20 |
Development Toolkits | ☑️ | ☑️ | ☑️ | ☑️ |
Archive Node Service | ☑️ | ☑️ | ☑️ | ☑️ |
Monitor Service | ☑️ | ☑️ | ☑️ | ☑️ |
Multi-Chain Support | ☑️ | ☑️ | ☑️ | ☑️ |
Token API | ☑️ | ☑️ | ☑️ | ☑️ |
NFT API | ☑️ | ☑️ | ☑️ | ☑️ |
Account API | - | ☑️ | ☑️ | ☑️ |
MemPool API | - | ☑️ | ☑️ | ☑️ |
Trace API | - | ☑️ | ☑️ | ☑️ |
For Free Tier, some APIs like Account API support 300 free trials.
Sui RPC APIs
For Sui RPC endpoint, each RPC call currently consumes 50 compute unit.
| Membership | Cost | Requests per Month | Rate Limit |
|---|---|---|---|
Free | $0 per month | 200,000 | 5 requests per second |
Lite | $29 per month | 2,000,000 | 10 requests per second |
Basic | $99 per month | 12,000,000 | 20 requests per second |
Pro | $199 per month | 40,000,000 | 40 requests per second |
Sui Indexing APIs
| Method | CU |
|---|---|
Retrieve Account's DeFi Portfolio | 400 |
Retrieve Account's Collections | 400 |
Retrieve a Single Collection Info | 400 |
Retrieve Collection Holders | 400 |
Retrieve Collection Activity | 400 |
Retrieve Collection NFT List | 400 |
Retrieve NFT Activity | 400 |
Retrieve NFT History Owner | 400 |
Retrieve Coin Holders | 400 |
Retrieve Account Activity | 400 |
Retrieve Account's Coins | 400 |
Retrieve Account's NFTs | 400 |
Retrieve Protocol Activity | 400 |
EVM RPC APIs
| Method | CU |
|---|---|
eth_chainId | 1 |
eth_syncing | 1 |
eth_protocolVersion | 1 |
net_listening | 1 |
eth_gasPrice | 1 |
eth_uninstallFilter | 10 |
eth_blockNumber | 10 |
eth_subscribe | 10 |
eth_unsubscribe | 10 |
eth_feeHistory | 10 |
eth_maxProrityFeePerGas | 10 |
eth_getTransactionReceipt | 15 |
eth_getTransactionReceiptsByBlockNumber | 15 |
eth_getUncleByBlockHashAndIndex | 15 |
eth_getUncleByBlockNumberAndIndex | 15 |
eth_getTransactionByBlockHashAndIndex | 15 |
eth_getTransactionByBlockNumberAndIndex | 15 |
eth_getUncleCountByBlockNumber | 15 |
eth_getUncleCountByBlockHash | 15 |
web3_clientVersion | 15 |
web3_sha3 | 15 |
eth_getBlockByNumber | 16 |
eth_getTransactionByHash | 17 |
eth_getStorageAt | 17 |
eth_getBalance | 19 |
eth_getCode | 19 |
eth_getBlockTransactionCountByHash | 20 |
eth_getBlockTransactionCountByNumber | 20 |
eth_getBlockByHash | 21 |
eth_getTransactionCount | 26 |
eth_call | 26 |
eth_getLogs | 75 |
eth_estimateGas | 80 |
eth_sendRawTransaction | 250 |
eth_getBlockReceipts | 500 |
Trace APIs
| Method | CU |
|---|---|
trace_block | 69 |
trace_transaction | 29 |
trace_get | 75 |
trace_call | 75 |
WebSocket
WebSocket subscriptions like eth_subscribe on BlockVision are priced based on bandwidth: the amount of data delivered as part of the subscription.
Each subscription type is priced identically, per byte:
| BandWidth | CU |
|---|---|
1 Byte | 0.02 |
On average, websocket subscriptions event sizes range from a minimum of about 75 bytes to a maximum of about 1000 bytes. Specifically, subscribing to newPendingTransactions costs about 2 compute units per event. The event bvPendingTransactions costs about 20 compute units, while newHeads requires about 25 compute units. But the actual situation may be far from this number.
Rate Limits (CUPS)
Rate limit serves to protect users from malicious actors or runaway scripts. Each tier has prioritized rate limit allocations designed for ultimate reliability. CUPS is a measure of the number of compute units used per second when making requests. Since each request is weighted differently, the query frequency is limited based on the total compute units used rather than the number of requests. For example, if you send one web3_sha3(15 CUs), two eth_blockNumber (16 CUs) requests in the same second, you will have a total of 47 CUPS.
| USER | Compute Units Per Second (CUPS) |
|---|---|
Free | 300 |
Lite | 500 |
Basic | 1000 |
Pro | 2000 |
Enterprise | Custom |
Last updated