Links

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

Feature
Free Tier
Lite Tier
Basic Tier
Pro Tier
Price
$0/Month
$29/Month
$99/Month
$199/Month
Compute Unit
10,000,000
100,000,000
600,000,000
1,500,000,000
Approx Request
400,000
4,000,000
24,000,000
60,000,000
Compute Units / Second
100
500
1,000
2,000
Max App
5
6
10
20
Development Toolkits
☑️
☑️
☑️
☑️
Archive Node Service
☑️
☑️
☑️
☑️
Monitor Service
☑️
☑️
☑️
☑️
Multi-Chain Support
☑️
☑️
☑️
☑️
FT API
☑️
☑️
☑️
☑️
NFT API
☑️
☑️
☑️
☑️
NFT Marketplace API
☑️
☑️
☑️
☑️
DeFi API
-
☑️
☑️
☑️
Portfolio API
-
☑️
☑️
☑️
Trace API
-
☑️
☑️
☑️
MemPool API
-
☑️
☑️
☑️
For Free Tier, some APIs like portfolio APIs support 300 free trials.

Basic 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
trace_callMany
200

FT APIs

Method
CU
erc20_totalSupply
30
erc20_banlance
30
erc20_metadata
50
erc20_transfers
75
erc20_mintsBurns
75
erc20_approvals
75
erc20_tokenPrice
75
erc20_balanceChangedList
75
erc20_accountPositions
100
eth_transfers
120
erc20_tokenHolders
150

Enhanced NFT APIs

Method
CU
nft_uri
30
nft_approvals
30
nft_approvalsForAll
30
nft_banlance
30
nft_listings
50
nft_floorPrice
50
nft_collectionFloorPrice
50
nft_isSuspicious
50
nft_collectionMarketInfo
50
nft_collectionOwners
75
nft_metadata
75
nft_transfers
75
nft_circulations
75
nft_owners
75
nft_mints
100
nft_accountStats
100
nft_contractStats
100
nft_collectionAuctionRecords
100
nft_accountAuctionRecords
100
nft_auctionRecords
100
nft_accountPositions
100
nft_volume
100
nft_collectionNfts
100
nft_accountTokenIDs
100
nft_topCollections
100
nft_topAccounts
100
nft_topBuyerAndSeller
100
nft_topNfts
100
nft_accountRentTokenIDs
100
nft_accountOwnedOrRentTokenIDs
200
nft_collectionHolders
200

Portfolio APIs

Method
CU
eth_getTransactionByAccount
200
account_defiPortfolio
100
account_ftPortfolio
100
account_nftPortfolio
100

Mempool APIs

Method
CU
eth_getBundleStat
100
eth_sendBundle
250
eth_callBundle
250

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
CUPS
Free
100
Lite
500
Basic
600
Pro
1500
Enterprise
Custom