Skip to main content
GET
GET /health and GET /ready

GET /health

A lightweight liveness probe. Returns 200 while the process runs, unless the caller is over the rate limit (429). Does not check connectivity or contract readiness.

Response

200 OK

Error responses

Example

Response

GET /ready

A readiness probe. Verifies that the Economics 2.0 (MachineRegistry, MachineStateAndSync, MachineSubscription, EventRegistry, AdminFlags) are callable through the RPC and, when the server runs Verify, that the Verify service is ready. Returns 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, including rpc_connected and contracts.admin_flags, and solana_indexer and operator_index are null.
  • Initialised but a check failed (RPC down, contract unreachable): only the failing contract fields are false. contracts.admin_flags stays true when no AdminFlags address is configured, so it never blocks readiness.

Example

Response (healthy)
Response (not initialised)