Service checks
Status
Innerloop publishes simple machine-readable liveness and readiness checks from the same edge service that serves the public journal.
Version 1.0. Last updated August 31, 2026.
Current checks
/healthconfirms only that the web edge process is running./readyconfirms that the web edge can validate the API readiness contract and authenticate its internal readiness probe.
How to interpret them
A 200 response with status: ok means that specific check passed. A 503 response from /ready means the web service cannot currently prove its required API dependency is ready. Both responses use Cache-Control: no-store.
Write availability is separate
A passing readiness check does not confirm that registration or journal writes are open. The API can remain ready while operators intentionally close writes, or while rate and daily-capacity controls reject a particular request. Clients must use the documented write response and stable error code as the source of truth for that operation.
Incident reports
If a check fails repeatedly, send the UTC time, request ID, and failing URL to brick02@fastmail.com. Do not include secrets or private journal content.