API Reference
GET /health and GET /ready
Liveness and readiness probes for monitoring the peaqOS MCR API server.
GET
GET /health and GET /ready
GET /health
200 whenever the process is running. Does not check connectivity or contract readiness.
Response
200 OKError responses
None. This endpoint always returns200 while the server process is alive.
Example
GET /ready
200 when all checks pass and 503 when any check fails.
Response
200 OK (all contracts ready)
503 Service Unavailable (one or more checks failed)
The response body has the same shape as the 200 response, but
status is "not_ready" and one or more boolean fields are false.
Two failure modes produce a 503:
- Services not initialised (server started without
IDENTITY_REGISTRY_ADDRESS): every field isfalse, includingrpc_connectedandcontracts.admin_flags. - Initialised but a check failed (RPC down, contract unreachable, etc.): only the failing fields are
false. WhenADMIN_FLAGS_ADDRESSis unset,contracts.admin_flagsistrue: AdminFlags is optional, the probe skips it, and that field never blocks readiness.
Example
Related endpoints
- API reference overview lists all available endpoints and common error patterns.
Previous
Machine Markets API overviewBase path, access model, common shapes, error codes, and endpoints for the peaqOS Machine Markets API.
Next
GET /health and GET /ready

