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 👇Documentation Index
Fetch the complete documentation index at: https://docs.rated.network/llms.txt
Use this file to discover all available pages before exploring further.
| Parameter | Context |
|---|---|
operatorId | The 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. |
idType | The 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. |
pool and node operator inputs are case sensitive. For example:❌ coinbase✅ CoinbaseBearer authentication header of the form Bearer <token>, where <token> is your auth token.
mainnet, hoodi, holesky depositAddress, withdrawalAddress, nodeOperator, pool, poolShare, entity, validator, privateSet Successful Response