Compare the roles.
| Role | What to inspect | Directory examples |
|---|---|---|
| Validator staking | Network, validator identity, current commission and participation | Solana, Cosmos Hub, Monad |
| Restaking / shared security | Operator, vault or service relationship and applicable conditions | Symbiotic, EigenLayer |
| Proving / confidential compute | Protocol-specific operator or prover record and environment | Fermah, Marlin, Interfold, Octra devnet |
| RPC access | Endpoint, chain identity, supported methods, limits and availability | Paid gateway not connected |
Why a validator listing is not an RPC offer.
A validator participates in a network’s operation. RPC is an interface for making network requests. A published validator address does not specify an RPC hostname, method policy, archive capability or rate limit. Those must be documented separately.
Where MPP and x402 fit.
MPP and x402 are payment protocols that can be used to authorize access to a resource. They do not determine which blockchain the RPC serves. Settlement details and the requested RPC network are separate configuration choices.
The Agent RPC page illustrates the request, payment challenge, authorization and response. It does not contact an upstream node or charge a wallet.
Choose the evidence relevant to the task.
For delegation, inspect the validator. For proving, inspect the prover. For an agent’s API call, inspect the endpoint specification and payment conditions once published. Start with the directory, which links the available source for each role.
Sources & review
By STAKR.space · Reviewed