> ## Documentation Index > Fetch the complete documentation index at: https://docs.beaconcha.in/llms.txt > Use this file to discover all available pages before exploring further. # Introduction > Rank, compare, and benchmark Ethereum staking entities using BeaconScore, APY, and missed rewards ## Overview Compare recognized Ethereum staking entities by operational performance, returns, and missed rewards. Reproduce the metrics published on [beaconcha.in/entities](https://beaconcha.in/entities). **What is an entity?** An entity is a named staking operator (e.g. Lido, Coinbase, Figment) whose validators are publicly labeled in the beaconcha.in dataset. The Entity Benchmarking APIs let you query performance, APY, missed rewards, and network-relative standing for any labeled entity, or for your own private validator set. *** ## Guides in This Section Rank all public entities by BeaconScore, net share, APY, or missed rewards. Includes pagination, filtering Unknown, and multi-window comparison. Compare one entity against the network baseline. Compute BeaconScore deltas, APY vs network, missed reward efficiency, and drill into sub-entities. Use a validator dashboard as a private entity. Benchmark any unlabeled or custom validator set against the network baseline using the same methodology. *** ## Key Metrics The leaderboard and benchmarking guides use four metric families. Each is fetched from a different endpoint: | Metric | Endpoint | What it measures | Used in | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **BeaconScore** | [`entities`](/api-reference/ethereum/entities/overview) / [`performance-aggregate`](/api-reference/ethereum/performance-aggregate) | Attestation, proposal, sync committee efficiency (luck-normalized; see [residual factors](/validator-dashboard/metric-validator-efficiency#residual-luck-factors)) | [Rank entities](/use-cases/rank-and-compare-entities#step-1-fetch-ranked-entities), [Benchmark vs network](/use-cases/benchmark-entity-vs-network#step-1-get-the-entity-beaconscore), [Private benchmarking](/use-cases/private-entity-benchmarking-with-dashboard#step-2-fetch-private-entity-beaconscore) | | **APY / ROI** | [`validators/apy-roi`](/api-reference/ethereum/validators/apy-roi) | Annualized return, split by CL and EL | [Rank entities](/use-cases/rank-and-compare-entities#step-2-fetch-apy--roi-per-entity), [Benchmark vs network](/use-cases/benchmark-entity-vs-network#step-4-fetch-apy-and-compare-vs-network), [Private benchmarking](/use-cases/private-entity-benchmarking-with-dashboard#step-5-fetch-apy--roi-for-the-private-set) | | **Missed rewards** | [`validators/rewards-aggregate`](/api-reference/ethereum/validators/rewards-aggregate) | ETH opportunity cost by duty type | [Rank entities](/use-cases/rank-and-compare-entities#step-3-fetch-missed-rewards-per-entity), [Benchmark vs network](/use-cases/benchmark-entity-vs-network#step-5-fetch-missed-rewards-and-compute-efficiency), [Private benchmarking](/use-cases/private-entity-benchmarking-with-dashboard#step-6-fetch-missed-rewards-for-the-private-set) | | **Network baseline** | [`performance-aggregate`](/api-reference/ethereum/performance-aggregate) (no entity filter) | Network-wide BeaconScore for delta computation | [Rank entities](/use-cases/rank-and-compare-entities#step-4-fetch-the-network-baseline), [Benchmark vs network](/use-cases/benchmark-entity-vs-network#step-2-get-the-network-baseline), [Private benchmarking](/use-cases/private-entity-benchmarking-with-dashboard#step-3-fetch-network-baseline) | *** ## BeaconScore Components BeaconScore integrates three validator duty types weighted by their contribution to rewards: | Component | Weight | | ------------------------- | ------ | | Attestation efficiency | 84.4% | | Proposal efficiency | 12.5% | | Sync committee efficiency | 3.1% | API references: [`entities`](/api-reference/ethereum/entities/overview) and [`performance-aggregate`](/api-reference/ethereum/performance-aggregate). Per-component efficiency can also be derived from [`rewards-aggregate`](/api-reference/ethereum/validators/rewards-aggregate) earned/missed ratios. See [Rank entities: Step 5](/use-cases/rank-and-compare-entities#step-5-compute-derived-metrics) and [Benchmark vs network: Step 5](/use-cases/benchmark-entity-vs-network#step-5-fetch-missed-rewards-and-compute-efficiency) for the calculation. BeaconScore and APY measure fundamentally different things. BeaconScore is a **duty efficiency** metric (0-100%): a score of 100% means the validator earned the maximum possible rewards for every assigned duty. APY is a **financial return** metric that expresses the annualized yield on staked ETH (e.g., 3%). A validator can have a perfect BeaconScore of 100% and an APY of 3% at the same time; these are not contradictory. BeaconScore normalizes for proposal luck (though some [residual luck factors](/validator-dashboard/metric-validator-efficiency#residual-luck-factors) remain), making it the recommended metric for cross-entity performance comparison. APY is better suited for reporting absolute returns. See [BeaconScore Calculation](/beaconscore/introduction) for the full formula and [BeaconScore vs. 3rd Party Metrics](/beaconscore/BeaconScore-vs-3rd-party-metrics) for how BeaconScore compares to other metrics. *** ## Missed Rewards Methodology Missed rewards quantify the **opportunity cost** of a validator failing a duty, not a balance penalty. All missed reward data comes from the [`rewards-aggregate`](/api-reference/ethereum/validators/rewards-aggregate) endpoint. The leaderboard uses: ``` CL missed = attestation missed (head + source + target) + sync committee missed + proposal missed (CL portion) EL missed = proposal missed (EL portion, foregone MEV + tips) Total missed = CL missed + EL missed % of earned = total_missed / (total_missed + earned_gross) x 100 ``` `earned_gross` is `data.total_reward` from `rewards-aggregate` (gross, before penalties). Do **not** use `data.total` (net) for this calculation. All wei values returned by `rewards-aggregate` are JSON strings. Cast with `int(str(v))` before dividing by `1e18`. For step-by-step implementation, see [Rank entities: Step 3](/use-cases/rank-and-compare-entities#step-3-fetch-missed-rewards-per-entity), [Benchmark vs network: Step 5](/use-cases/benchmark-entity-vs-network#step-5-fetch-missed-rewards-and-compute-efficiency), or [Private benchmarking: Step 6](/use-cases/private-entity-benchmarking-with-dashboard#step-6-fetch-missed-rewards-for-the-private-set). For per-validator missed reward analysis, see [Analyze Missed Rewards](/use-cases/missed-rewards). *** ## vs Average Thresholds The leaderboard uses the following thresholds consistently across all comparisons (BeaconScore total, all three components, and APY deltas). See these applied in [Rank entities: Step 5](/use-cases/rank-and-compare-entities#step-5-compute-derived-metrics), [Benchmark vs network: Step 3](/use-cases/benchmark-entity-vs-network#step-3-compute-beaconscore-delta), and [Private benchmarking: Step 4](/use-cases/private-entity-benchmarking-with-dashboard#step-4-compute-beaconscore-delta): | Color | Condition | | --------- | ---------------------------------------------------------- | | 🟢 Green | `delta >= +0.0025` (+0.25 percentage points above network) | | 🟡 Yellow | `-0.0025 < delta < +0.0025` (within ±0.25pp of network) | | 🔴 Red | `delta <= -0.0025` (more than 0.25pp below network) | For missed reward efficiency (lower = better): | Color | Condition | | --------- | ------------------------- | | 🟢 Green | `< 0.40%` of earned | | 🟡 Yellow | `0.40% – 0.60%` of earned | | 🔴 Red | `> 0.60%` of earned | *** ## Evaluation Windows All benchmarking endpoints support the same rolling windows: | Window | Typical use | | ------ | --------------------------------- | | `24h` | Incident detection | | `7d` | Weekly review | | `30d` | Monthly leaderboard (recommended) | | `90d` | Long-term trend analysis | Use consistent windows when comparing entities. `all_time` is not supported for entity endpoints. *** ## API Plan Requirements | Endpoint | Minimum plan | | ------------------------------------------------------------------------------------------------------------------ | ------------ | | [`entities`](/api-reference/ethereum/entities/overview) | Scale | | [`entity/sub-entities`](/api-reference/ethereum/entity/sub-entities) | Scale | | [`validators/apy-roi`](/api-reference/ethereum/validators/apy-roi) with `entity` selector | Scale | | [`validators/rewards-aggregate`](/api-reference/ethereum/validators/rewards-aggregate) with `entity` selector | Scale | | [`performance-aggregate`](/api-reference/ethereum/performance-aggregate) (network baseline) | Any | | [`validators/performance-aggregate`](/api-reference/ethereum/validators/performance-aggregate) with `dashboard_id` | Any | See [API Pricing](https://beaconcha.in/pricing) for plan details. *** ## Attribution If you display BeaconScore publicly, follow the [BeaconScore License](/legal/beaconscore-license) and [License Materials](/legal/license-materials). *** ## Related Resources * [Supported Entities List](https://beaconcha.in/entities) * [BeaconScore vs. 3rd Party Metrics](/beaconscore/BeaconScore-vs-3rd-party-metrics) * [BeaconScore Calculation](/beaconscore/introduction) * [APY & ROI Metrics](/use-cases/apy-roi) * [Analyze Missed Rewards](/use-cases/missed-rewards) * [Dashboard as Private Sets](/use-cases/rewards-dashboard-private-sets#dashboard-as-private-sets) * [Validator Tagging](/validator-tagging/overview)