💎 Overview
Returns an overview of all entities with their validator count, BeaconScore, and net share.
Use case guide: Entity benchmarking explains how to rank entities and compare an operator with the network baseline.
Results can be sorted by beaconscore, net_share, validator_count, or sub_entity_count in ascending or descending order.
By default, results are sorted by net_share in descending order.
Note: The underlying data is precomputed and updated hourly. all_time evaluation window is not supported for this endpoint.
Premium Endpoint: This endpoint requires a Scale or Enterprise plan.
Attribution Required: If you display BeaconScore data publicly, you must include appropriate attribution. See our BeaconScore License and License Materials for badges and usage guidelines.
Authorizations
Body
The Ethereum chain to query.
mainnet, hoodi Opaque continuation token from a previous response.
For machine metrics this token stores series-specific continuation state for system_metrics, validator_metrics,
and node_metrics rather than a single shared list position.
Number of items to return per metric array. Defaults to 10 when omitted.
1 <= x <= 10The field to sort entities by.
beaconscore: Sort by BeaconScore (validator efficiency)net_share: Sort by network share (default)validator_count: Sort by number of validatorssub_entity_count: Sort by number of sub-entities
beaconscore, net_share, validator_count, sub_entity_count The sort order for the results.
asc: Ascending order (lowest first)desc: Descending order (highest first, default)
asc, desc Response
Successful response.
Response containing an overview of entities with their validator count, BeaconScore, and net share.
Unix timestamp indicating when the entities data was last computed. The underlying data is precomputed and updated hourly.
x >= 0The time span actually covered by the returned results — from the first to the last matching data point — specified in slots, epochs, and Unix timestamps.
This reflects the data that was found, not the range that was queried. When no data is found, it falls back to the requested range, or to the full available history if no range was given.

