/v1/eth/validators/consolidations
/v1/eth/entityConsolidations
/v1/eth/consolidationCapacity
/v1/eth/consolidationCapacity/entity
BABY
.GET /v1/babylon/validators/{validator_address}/rewards
validator_address
/v1/babylon/network/rewards
/v1/babylon/validators/{validator_address}/state
validator_address
/v1/babylon/delegators/{delegator_address}/state
delegator_address
per validator they are delegated toDOT
.GET /v1/polkadot/validators/{validator_address}/rewards
stashAccountAddress
which is what we are considering as the validator_address
./v1/polkadot/network/rewards
ADA
.GET /v1/cardano/validators/{pool_id}/rewards
pool_id
pool_id
can either be the human-readable version in the form of ‘pool’ + 52 characters (e.g. pool1z5uqdk7dzdxaae5633fqfcu2eqzy3a3rgtuvy087fdld7yws0xt
) or the hashed version of this pool_id
(e.g153806dbcd134ddee69a8c5204e38ac80448f62342f8c23cfe4b7edf
). This is called poolHashId
in the response./v1/cardano/network/rewards
GET /v1/celestia/validators/{node_id}/rewards
GET /v1/celestia/network/rewards
GET /v1/avalanche/validators/{node_id}/rewards
GET /v1/avalanche/network/rewards
ethPrice
and usdPrice
being returned by our Eigenlayer rewards endpoints has been fixed. Specifically these endpoints are:/v1/eigenlayer/entities/{operator_address}/rewards/
/v1/eigenlayer/delegators/{delegator_address}/rewards/
/v1/eigenlayer/eigenpods/{eigenpod_address}/rewards
activatedAt
) and the related token has the appropriate liquidity.Rest assured that we have taken steps to ensure that instances like this are minimized moving forward.If you have any questions or feedback, feel free to go to feedback.rated.network.For more information on our API endpoints, please see our documentation.6869
.Stay tuned for more releases regarding billing and usage transparency.For more information on our pricing and the computation of compute units, please see here.ethPrice
and usdPrice
being returned by our Eigenlayer rewards endpoints below:/v1/eigenlayer/entities/operator_address/rewards/
/v1/eigenlayer/delegators/delegator_address/rewards/
/v1/eigenlayer/eigenpods/eigenpod_address/rewards/
amount
field to measure the rewards for the corresponding token information being given in the response.We apologize for any inconvenience this may have caused and will immediately keep you all updated as we address this issue in the coming week (week of January 20, 2025).v1/eigenlayer/rewardsApiMetadata
endpoint. Previously, this returned metadata specific to the latest complete rewards data available from our Eigenlayer rewards APIs. With the release of our new daily stake state endpoints, we have now turned this endpoint into a more generalized one. Two main changes below.New name: v1/eigenlayer/apiMetadata
Old name: v1/eigenlayer/rewardsApiMetadata
v1/eigenlayer/eigenpods/eigenpod_address/state
v1/eigenlayer/entities/operator_address/state
v1/eigenlayer/delegators/delegator_address/state
utc=true
to your existing API queries. That’s it!Note: UTC data is available for dates from October 1, 2024 onwardsHere’s an example of how this would work 👇 When querying Coinbase’s effectiveness from Nov 1-7 2024, you’ll receive data in daily UTC intervals.
GET /v1/eigenlayer/eigenpods/address/rewards
GET /v1/eigenlayer/entities/entity_id/rewards
Provides the rewards earned by an entity (operator) across all networks over a specified time period
GET /v1/eigenlayer/delegators/address/delegations
GET /v1/eigenlayer/operators/operator_id/delegations
Returns operator delegation data, detailing delegator addresses, Eigenpod addresses, and the time periods for which the operator had delegated stake
ThesyncSignatureCount
field has been added to the/v1/eth/entities/\{entity_id\}/attestations
endpoint, providing a more complete view of validator performance in the sync committee. This field was previously only available in the/v1/eth/validators/\{validator_index_or_pubkey\}/attestations
endpoint
Resolved a 500 error occurring when using thefrom
parameter in thechainDailyRewards
endpoint, caused by a datatype mismatch (int vs. string)
Added a newchainDailyRewards
endpoint based on Ethereum chain days, in addition to the existingdailyRewards
endpoint which is based on UTC days
v0/eth/network/chainDailyRewards
and v0/eth/network/chainDailyRewards/{day}
The v0/eth/network/chainDailyRewards
endpoint now includes the latest total effective balance of validators, providing more insight into validator performance
IntroducedstartSlot
,endSlot
,startTimestamp
, andendTimestamp
fields to rewards endpoint
Modified the data type for execution reward columns (e.g.,sum_priority_fees_wei
andsum_baseline_mev_wei
) fromStrictInt
toDecimal
to improve accuracy.
/v1/eth/validators/{validator_index_or_pubkey}/effectiveness
/v1/eth/validators/{validator_index_or_pubkey}/attestations
/v1/eth/validators/{validator_index_or_pubkey}/proposals
/v0/eth/validators/{validator_index_or_pubkey}/effectiveness
Predicted Withdrawal Endpoints/v0/eth/withdrawals/predicted/operators/{operator_id}
/v0/eth/withdrawals/predicted/operators/{operator_id}
Key Resources - API Reference
For support inquiries, please contact us at hello@rated.network. If you have feedback, we would love to hear from you at feedback.rated.network!
/v0/eth/blocks
/v0/eth/blocks/{consensus_slot}
Key Resources - API ReferenceFor support inquiries, please contact us at hello@rated.network. If you have feedback, we would love to hear from you at feedback.rated.network!To create a tag, initiate a POST request to /v1/eth/tags with your desired validators
/v0/eth/blocks
/v0/eth/blocks/{consensus_slot}
/v0/eth/blocks
/v0/eth/blocks/{consensus_slot}
/v0/eth/validators/{validator_index_or_pubkey}/effectiveness
/v0/eth/validators/effectiveness
/v0/eth/validators/{validator_index_or_pubkey}/apr
/v0/eth/operators/{operator_id}/effectiveness
/v0/eth/operators/{operator_id}/apr
/v0/eth/network/overview
Important links 👇Previous Allowance: 100,000 compute units per month.
Allowance: 100,000 base compute units per month.
In response to user feedback, the Pro Tier will be discontinued. Users have expressed a preference for the Enterprise Tier, which offers greater flexibility and is better suited to their needs.The Terms of Service have been updated to reflect these changes. These updates took effect on February 13, 2024. Users are encouraged to review the new terms.You can view the plans in detail by visiting the console or docs.If you’d like support or have questions, please reach out via hello@rated.network.