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 while the process runs, unless the caller is over the rate limit (429). Does not check connectivity or contract readiness.
Response
200 OKError responses
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 its contract addresses): every field is
false, includingrpc_connectedandcontracts.admin_flags, andsolana_indexerandoperator_indexarenull. - Initialised but a check failed (RPC down, contract unreachable): only the failing contract fields are
false.contracts.admin_flagsstaystruewhen no AdminFlags address is configured, so it never blocks readiness.
Example
Related endpoints
- API reference overview lists all available endpoints and common error patterns.

