API Reference
GET /operator/{did}/machines
List all machines an operator owns or controls, with paginated MCR scores.
GET
GET /operator/{did}/machines
Endpoint
mcr: "Provisioned" and mcr_score: 0: the listing does not read its indexed events, so use GET /mcr/{did} for its rating. A Solana-homed machine is listed under the peaq operator address recorded on its machine account, the operator that GET /machine/{did} returns; a machine with no operator set is not listed.
The server reads which machines an address owns from an ownership index, then reads each listed machine’s data and score from the chain. A background worker builds the peaq half from MachineRegistry events up to the finalized block and polls about once a minute; the Solana half is a periodic snapshot of Solana-homed machines. On a 200 the index is at most 100 blocks behind the chain head as the worker last read it, and index in the body says how far; the gap to the current chain grows with index.head_observed_age_seconds. The route answers 503 instead of a list when the peaq half is more than 100 blocks behind, when its worker has not read the chain head for more than ten poll intervals (about ten minutes), or when the Solana snapshot is out of date. Large fleets iterate offset instead of asking for the whole list in one response.
Path parameters
string
required
Operator DID (
did:peaq:0x...) or raw EVM address (0x...)Query parameters
integer
default:"0"
Number of machines to skip before the returned page. Must be
>= 0.integer
default:"20"
Maximum number of machines to return per page. Range
1-20.Response
200 OK
A page can hold fewer entries than
limit. A peaq-homed machine that no longer exists is skipped, and a machine the server could not read (including a Solana-homed machine that is relocating) is left out and counted in unreadable, so a non-zero unreadable means the page is incomplete for a reason other than ownership.
An operator with no machines returns 200 with an empty machines array and pagination.total of 0.
Error responses
Example
Related endpoints
GET /mcr/{did}returns detailed MCR data for a single machine, including revenue trend and summary.GET /machine/{did}returns the full machine profile.

