API Reference

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 Unit10,000,000100,000,000600,000,0001,500,000,000
EVM Approx. Request400,0004,000,00024,000,00060,000,000
Compute Units / Second3005001,0002,000
Max App561020
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.

MembershipCostRequests per MonthRate Limit
Free$0 per month200,0005 requests per second
Lite$29 per month2,000,00010 requests per second
Basic$99 per month12,000,00020 requests per second
Pro$199 per month40,000,00040 requests per second

Sui Indexing APIs

MethodCU
Retrieve Account's DeFi Portfolio400
Retrieve Account's Collections400
Retrieve a Single Collection Info400
Retrieve Collection Holders400
Retrieve Collection Activity400
Retrieve Collection NFT List400
Retrieve NFT Activity400
Retrieve NFT History Owner400
Retrieve Coin Holders400
Retrieve Account Activity400
Retrieve Account's Coins400
Retrieve Account's NFTs400
Retrieve Protocol Activity400

EVM RPC APIs

MethodCU
eth_chainId1
eth_syncing1
eth_protocolVersion1
net_listening1
eth_gasPrice1
eth_uninstallFilter10
eth_blockNumber10
eth_subscribe10
eth_unsubscribe10
eth_feeHistory10
eth_maxProrityFeePerGas10
eth_getTransactionReceipt15
eth_getTransactionReceiptsByBlockNumber15
eth_getUncleByBlockHashAndIndex15
eth_getUncleByBlockNumberAndIndex15
eth_getTransactionByBlockHashAndIndex15
eth_getTransactionByBlockNumberAndIndex15
eth_getUncleCountByBlockNumber15
eth_getUncleCountByBlockHash15
web3_clientVersion15
web3_sha315
eth_getBlockByNumber16
eth_getTransactionByHash17
eth_getStorageAt17
eth_getBalance19
eth_getCode19
eth_getBlockTransactionCountByHash20
eth_getBlockTransactionCountByNumber20
eth_getBlockByHash21
eth_getTransactionCount26
eth_call26
eth_getLogs75
eth_estimateGas80
eth_sendRawTransaction250
eth_getBlockReceipts500

Trace APIs

MethodCU
trace_block69
trace_transaction29
trace_get75
trace_call75

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:

BandWidthCU
1 Byte0.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.

USERCompute Units Per Second (CUPS)
Free300
Lite500
Basic1000
Pro2000
EnterpriseCustom