GET
/
v0
/
eth
/
operators
/
{operator_id}
/
relayers
curl --request GET \
  --url https://api.rated.network/v0/eth/operators/{operator_id}/relayers \
  --header 'Authorization: Bearer <token>'
[
  {
    "percentage": 0.00041296716911005574,
    "relayer": "agnostic"
  }
]

This endpoints returns information relating to an entity’s historical distribution of relays they have procured blocks from.

Here’s how to interpret the inputs required to operate it 👇

ParameterContext
operatorIdThe name of the entity in question. This could be deposit address, a node operator, or a pool. Please see our docs to get a better understanding of how we aggregate validators.
windowThe time window of aggregation. You might ask for 1d, 7d, 30d or All-time data.
idTypeThe type of entity class you would like returned. You might ask for pool, poolShare, nodeOperator, depositAddress, or withdrawalAddress. Note: it is optional and can be inferred automatically for pools, pool shares and node operators. It defaults to depositAddress if it is missing and an address is provided.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
X-Rated-Network
enum<string>
Available options:
mainnet,
hoodi,
holesky

Path Parameters

​
operator_id
string
required

Query Parameters

​
idType
enum<string> | null
Available options:
depositAddress,
withdrawalAddress,
nodeOperator,
pool,
poolShare,
entity,
validator,
privateSet
​
window
enum<string>
Available options:
1d,
7d,
30d,
all

Response

200
application/json

Successful Response

The response is of type RelayerPercentage · object[].

GET
/
v0
/
eth
/
operators
/
{operator_id}
/
relayers
curl --request GET \
  --url https://api.rated.network/v0/eth/operators/{operator_id}/relayers \
  --header 'Authorization: Bearer <token>'
[
  {
    "percentage": 0.00041296716911005574,
    "relayer": "agnostic"
  }
]

This endpoints returns information relating to an entity’s historical distribution of relays they have procured blocks from.

Here’s how to interpret the inputs required to operate it 👇

ParameterContext
operatorIdThe name of the entity in question. This could be deposit address, a node operator, or a pool. Please see our docs to get a better understanding of how we aggregate validators.
windowThe time window of aggregation. You might ask for 1d, 7d, 30d or All-time data.
idTypeThe type of entity class you would like returned. You might ask for pool, poolShare, nodeOperator, depositAddress, or withdrawalAddress. Note: it is optional and can be inferred automatically for pools, pool shares and node operators. It defaults to depositAddress if it is missing and an address is provided.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
X-Rated-Network
enum<string>
Available options:
mainnet,
hoodi,
holesky

Path Parameters

​
operator_id
string
required

Query Parameters

​
idType
enum<string> | null
Available options:
depositAddress,
withdrawalAddress,
nodeOperator,
pool,
poolShare,
entity,
validator,
privateSet
​
window
enum<string>
Available options:
1d,
7d,
30d,
all

Response

200
application/json

Successful Response

The response is of type RelayerPercentage · object[].