Skip to main content
GET
GET /solana/mcr/{solana_addr}

Endpoints

Both endpoints key the existing MCR reads by a Solana address. The server resolves the address through the peaq binding registry on Solana mainnet (program GrsCoPkeLUAoXjuwPfCcuch77Chco1Gx95zCCQNYGqG6, one getAccountInfo read of the reverse-lookup account at finalized commitment) to the bound peaq EVM identity, then serves the same payload as GET /mcr/{did} or GET /operator/{did}/machines. Scoring inputs always come from peaq; Solana is used for identity resolution only. No chain writes. A machine or operator binds its Solana wallet to its peaq address with a dual-signed bind instruction on that program (a permissionless, trustless instruction: no peaq key is involved). The SDK and CLI do not expose the binding write yet; peaq runs it for partner fleets. See Omni-chain: Solana.

Path parameters

string
default:"2hga7WjszaFHAkiUGngLvY16ebtkrKwCeTSGYv9uzK8p"
required
Base58-encoded 32-byte Solana public key.

Query parameters (operator endpoint only)

integer
default:"0"
Zero-based offset into the operator’s machine list.
integer
default:"20"
Page size, 1 to 20.

Response

200 OK: the GET /mcr/{did} payload (or the operator listing) plus two fields:
An operator with no machines returns an empty machines list, not an error.

Resolution errors

Once resolution succeeds, every downstream error is the EVM endpoint’s own. Settled outcomes (bound, not_bound, binding_revoked) are cached for 60 seconds, so a just-activated or just-revoked binding can lag by up to one minute.

Examples

These endpoints serve Tokenomics 1.0 machines (address DIDs). The Economics 2.0 MCR server that is rolling out disables the /solana/* routes until it has its own binding resolver. Treat them as 1.0 surface.