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:

(Content Length BytesWeight)+(Item Count×Business Value×Parameter Multiplier)\left(\frac{\text{Content Length Bytes}}{\text{Weight}}\right) + \left(\text{Item Count} \times \text{Business Value} \times \text{Parameter Multiplier}\right)

​
Why use Compute Units?

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.

​
How to Monitor Your Compute Unit (CU) Consumption

You can track your compute unit usage in two ways:

  1. API Response Headers: Every API request you make includes the x-rated-compute-units header in the response. This header displays the exact number of CUs consumed by that specific request.

  2. Rated Console Dashboard:

    • View your overall CU usage on the main Dashboard
    • See detailed CU consumption per endpoint in the Usage Limits page (navigate via Settings → Usage Limits)

​
Autoscale Compute

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.

TierBase Monthly Compute Units (CU)Price per 1M CUs over base CUsAutoscale allowance (upper bound)
Starter100,000❌❌
Build1,000,000$1503,000,000
Growth4,000,000$1258,000,000
EnterpriseCustomCustomCustom

​
Weights per Endpoint

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.

EndpointWeightBusiness ValueParameter MultiplierMultiplier
/v1/eth85null
/v1/eth/effectiveness85null
/v1/eth/rewards85null
/v1/eth/geographicalDistributions810null
/v1/eth/hostDistributions810null
/v1/eth/entities85null
/v1/eth/entities/summaries82null
/v1/eth/entities/{entity_id}/summaries82null
/v1/eth/entities/{entity_id}/effectiveness810null
/v1/eth/entities/{entity_id}/attestations810null
/v1/eth/entities/{entity_id}/proposals810null
/v1/eth/entities/{entity_id}/rewards810null
/v1/eth/entities/{entity_id}/penalties810null
/v1/eth/entities/{entity_id}/mappings210null
/v1/eth/entities/{entity_id}/aprs210null
/v1/eth/entities/{entity_id}/slashings210null
/v1/eth/validators410null
/v1/eth/validators/{validator_index_or_pubkey}810null
/v1/eth/validators/{validator_index_or_pubkey}/effectiveness810null
/v1/eth/validators/{validator_index_or_pubkey}/attestations810null
/v1/eth/validators/{validator_index_or_pubkey}/proposals810null
/v1/eth/validators/{validator_index_or_pubkey}/rewards810null
/v1/eth/validators/{validator_index_or_pubkey}/penalties810null
/v1/eth/validators/{validator_index_or_pubkey}/withdrawals810null
/v1/eth/validators/{validator_index_or_pubkey}/mappings210null
/v1/eth/validators/{validator_index_or_pubkey}/aprs810null
/v1/eth/validators/effectiveness410null
/v1/eth/validators/attestations410null
/v1/eth/validators/proposals410null
/v1/eth/validators/mappings210null
/v1/eth/validators/slashings410null
/v1/sets/{id}/effectiveness410null
/v1/sets/{id}/attestations410null
/v1/sets/{id}/proposals410null
/v1/sets/{id}/rewards410null
/v1/sets/{id}/penalties410null
/v1/solana/delegators/stakeAccounts/{stake_account}/rewards85null
/v1/solana/delegators/stakeAuthorities/{stake_authority}/rewards85null
/v1/solana/network/overview85null
/v1/solana/network/validatorDistributions85null
/v1/solana/network/effectiveness85null
/v1/solana/validators/{validator_id}/rewards15null
/v1/solana/validators/{validator_id}/performance15null
/v1/solana/validators/{validator_id}/performance/latency15null
/v1/solana/validators/leaderboard85null
/v1/solana/validators/{validator_id}82null
/v1/solana/validators/{validator_id}/delegators252null
/v1/solana/validators85null
/v1/solana/validators/{validator_id}/summary82null
/v1/eigenlayer/delegators/{address}/delegations1500null
/v1/eigenlayer/entities/{entity_id}/delegations1500null
/v1/eigenlayer/eigenpods/{address}/rewards1500granularity=week5
/v1/eigenlayer/delegators/{address}/rewards11200granularity=week5
/v1/eigenlayer/entities/{entity_id}/rewards11200granularity=week5
/v1/eigenlayer/eigenpods/{address}/state1500null
/v1/eigenlayer/operators/{address}/state11200null
/v1/cosmos/validators/{validator_address}/rewards210null
/v1/cosmos/network/rewards210null
/v1/avalanche/validators/{node_id}/rewards210null
/v1/avalanche/network/rewards210null
/v1/celestia/validators/{validator_address}/rewards210null
/v1/celestia/network/rewards210null
/v1/cardano/validators/{pool_id}/rewards210null
/v1/cardano/network/rewards210null
/v1/polkadot/validators/{validator_address}/rewards210null
/v1/polkadot/network/rewards210null

For the endpoint /v1/tags/{id}/validators, we will calculate compute units as 128 pubkeys reported