GET
/
v0
/
eth
/
operators
/
{operator_id}

his endpoint returns profile information on specific operators. It’s still relatively nascent, but expect this to be enriched with all kinds of useful information in the coming quarters.

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 withdrawal address, a node operator, or a pool. Please see our docs to get a better understanding of how we aggregate validators.
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.

The pool and node operator inputs are case sensitive. For example:

❌ coinbase

✅ Coinbase

Headers

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

Path Parameters

​
operator_id
string
required

Query Parameters

​
idType
enum<string> | null
Available options:
depositAddress,
withdrawalAddress,
nodeOperator,
pool,
poolShare,
entity,
validator,
privateSet

Response

200
application/json
​
id
string
required
​
idType
enum<string>
required
Available options:
depositAddress,
withdrawalAddress,
nodeOperator,
pool,
poolShare,
entity,
validator,
privateSet
​
displayName
string
required
​
operatorTags
object[]
required
​
nodeOperatorCount
integer | null
required
Required range: x > 0
Percentile ranksOperator effectiveness