Compute Units
All you need to know about the fundamental unit of account Rated API v1.
Last updated
All you need to know about the fundamental unit of account Rated API v1.
Last updated
Compute Units are a metric reflecting the computational resources utilized by each API request. Some queries, like /apr, are quick and lightweight, while others, such as /operators/{operator_id}/effectiveness, may be more resource-intensive.
Compute Units for each endpoint are determined using the following formula:
We wanted to find an approach that guarantees fairness and scalability, ensuring that the costs align with the real value our users get from the APIs. By basing costs on compute units, we ensure that you receive the most transparent and equitable pricing. As we continue to innovate and evolve, we remain focused on delivering both top-notch services and clear, fair pricing that benefits our users.
Turning on autoscale gives you instant access to additional compute units beyond your base monthly compute units allowance. This is to cover scenarios such as spikes in traffic, scenario testing and more! Autoscale gives you the scalability you need at affordable prices.
Build
1,000,000
$150
3,000,000
Growth
4,000,000
$125
8,000,000
Pro (Monthly)
12,000,000
$100
20,000,000
Pro (Yearly)
12,000,000
$75
20,000,000
Enterprise
Custom
Custom
Custom
This represents the weight component of compute unit calculation used per endpoint. Note that your specific averages compute units per endpoint will vary based on your usage patterns of the endpoints and the kinds of aggregations you perform.
/v0/eth/network/overview
8
/v0/eth/network/stats
8
/v0/eth/network/capacity
8
/v0/eth/network/capacity/pool
8
/v0/eth/p2p/geographical
8
/v0/eth/p2p/hostingProvider
8
/v0/eth/operators
8
/v0/eth/operators/percentiles
8
/v0/eth/operators/{operator_id}
8
/v0/eth/operators/{operator_id}/effectiveness
8
/v0/eth/operators/{operator_id}/apr
8
/v0/eth/operators/{operator_id}/summary
8
/v0/eth/operators/{operator_id}/stakeMovement
8
/v0/eth/operators/{operator_id}/clients
8
/v0/eth/operators/{operator_id}/relayers
8
/v0/eth/validators/effectiveness
8
/v0/eth/validators/{validator_index_or_pubkey}
8
/v0/eth/validators/{validator_index_or_pubkey}/effectiveness
32
/v0/eth/validators/{validator_index_or_pubkey}/apr
32
/v0/eth/blocks
32
/v0/eth/blocks/{consensus_slot}
32
/v0/eth/relayers
32
/v0/eth/relayers/recent
32
/v0/eth/relayers/stats
32
/v0/eth/trending/effectiveness/operators
32
/v0/eth/trending/mev/operators
32
/v0/eth/trending/effectiveness/validators
32
/v0/eth/trending/slashings/operators
32
/v0/eth/slashings/overview
32
/v0/eth/slashings/leaderboard
32
/v0/eth/slashings/cohortAnalysis
32
/v0/eth/slashings/timeseries
32
/v0/eth/slashings
32
/v0/eth/slashings/{validator_index_or_pubkey}
32
/v0/polygon/network/overview
8
/v0/polygon/validators
8
/v0/polygon/validators/{validator_id}
8
/v0/polygon/validators/{validator_id}/effectiveness
8
/v0/polygon/validators/{validator_id}/summary
8
/v0/polygon/delegators
8
/v0/polygon/delegators/{delegator_address}/summary
8
/v0/polygon/delegators/{delegator_address}/rewards
8
/v1/sets/{id}/effectiveness
4
/v1/sets/{id}/attestations
4
/v1/sets/{id}/proposals
4
/v1/sets/{id}/rewards
4
/v1/sets/{id}/penalties
4
Note: for the endpoint /v1/tags/{id}/validators, we will calculate compute units as 128*{pubkeys reported}
