Skip to main content
GET
GET /machine/{did}

Endpoint

Returns the full machine profile for a . The response includes identity, , , and data visibility-dependent fields. This endpoint shares its response builder with GET /metadata/; both return the same shape.

Path parameters

string
required
Machine DID (did:peaq:0x...) or raw EVM address (0x...)

Response

200 OK — base fields (always present)

Additional fields by data visibility

The data_visibility value on the machine’s DID document determines which additional fields appear in the peaqos object.

data_visibility == "private"

data_visibility == "onchain"

Each element in event_data:

data_visibility == "public"

The server fetches live data from the machine’s data_api URL with a 5-second timeout. The URL is validated before the request is made: private IP ranges, loopback addresses, link-local addresses, reserved ranges, multicast addresses, and known cloud metadata endpoints (169.254.169.254, metadata.google.internal) are blocked. Redirects are not followed. Responses must be valid JSON objects no larger than 1 MB. On success: On failure: Possible partner_data_error values:

Error responses

Example

Response (private visibility)
Response (onchain visibility)
Response (public visibility, fetch failure)
  • GET /mcr/ returns a focused MCR score response with revenue trend and summary.
  • GET /metadata/ returns the same response shape, resolved by NFT token ID instead of DID.
  • GET /machines/ returns the peaqOS Machine Card resolved by numeric machine ID.