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
Basic Tier
Pro Tier
Enterprise Tier
Price
$0/Month
$99/Month
$199/Month
Custom
Compute Unit
10,000,000
600,000,000
1,500,000,000
Custom
Approx Request
400,000
24,000,000
60,000,000
Custom
Throughput (Compute Units / Second)
100
600
1500
Custom
Max App
5
10
20
No Limited
Max Alert
2
10
20
No Limited
Development Toolkits
☑️
☑️
☑️
☑️
Archive Node Service
☑️
☑️
☑️
☑️
Monitor Service
☑️
☑️
☑️
☑️
Multi-Chain Support
☑️
☑️
☑️
☑️
24/7 Support
☑️
☑️
☑️
ERC20 Dataset
☑️
☑️
☑️
ERC721 and ERC1155 Dataset
☑️
☑️
☑️
Portfolio and Position APIs
☑️
☑️
☑️
Trace and Debug APIs
☑️
☑️
☑️
Enhanced NFT APIs
☑️
☑️
☑️
Price API
☑️
☑️
Hot dApp APIs
☑️
☑️
☑️
Exclusive Customized Services
☑️
For Free Tier, some APIs like enhanced NFT APIs support 300 free trials.

Basic APIs

Method
CU
eth_chainId
1
eth_syncing
1
eth_protocolVersion
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_getUncleByBlockHashAndIndex
15
eth_getUncleByBlockNumberAndIndex
15
eth_getTransactionByBlockHashAndIndex
15
eth_getTransactionByBlockNumberAndIndex
15
web3_sha3
15
eth_getBlockByNumber
16
eth_getTransactionByHash
17
eth_getStorageAt
17
eth_getBalance
19

Enhanced APIs

Method
CU
eth_issuance
50
eth_getModifiedAccountsByNumber
500
eth_getModifiedAccountsByHash
500
eth_getTransactionByAccount
1000
trace_block
2000
trace_transaction
1000
trace_get
200
trace_call
200
trace_callMany
500
trace_replayBlockTransactions
2000
trace_replayTransaction
1000
trace_filter
500
debug_accountRange
800
debug_accountAt
800
debug_getModifiedAccountsByNumber
400
debug_getModifiedAccountsByHash
400
debug_storageRangeAt
1000
debug_traceBlockByHash
2000
debug_traceBlockByNumber
2000
debug_traceTransaction
500

ERC APIs

Method
CU
erc20_accountPositions
500
erc20_approvals
100
erc20_banlance
100
erc20_mintsBurns
100
erc20_totalSupply
50
erc20_transfers
100
erc20_metadata
100
erc20_filterAccounts
5000

Enhanced NFT APIs

Method
CU
nft_metadata
100
nft_collectionAuctionRecords
200
nft_accountAuctionRecords
200
nft_auctionRecords
200
nft_topCollections
500
nft_topAccounts
500
nft_topNfts
500
nft_volume
200
nft_uri
100
nft_mints
100
nft_accountTokenIDs
500
nft_filterAccounts
800
nft_approvals
50
nft_banlance
100
nft_transfers
100
nft_accountStats
200
nft_contractStats
200
nft_accountPositions
500
nft_owners
500
nft_circulations
100

Portfolio APIs

Method
CU
ft_portfolio
800
nft_portfolio
1000

Price APIs

Method
CU
token_price
50

dApp APIs

Currently, each APIs is calculated at 100 CU.

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
Standard
600
Pro
1500
Enterprise
Custom