s46.apiv1

Operations

Liveness, readiness, and support routes.

The control plane and gateway expose the same status checks. Neither requires authentication.

Liveness

GET/healthz→ 200

Reports process liveness, not model availability:

{ "status": "ok" }

Readiness

GET/readyz→ 200 / 503
curl -i https://api.s46.dev/readyz

Readiness requires a reachable database when configured and current independent registry verification when enabled. A healthy database or persisted catalog alone does not establish model readiness.

HTTPBodyMeaning
200{ "status": "ok", "database": "ok" }Configured checks passed.
200{ "status": "ok", "database": "disabled" }No database configured; any enabled registry check passed.
503{ "status": "unavailable", "database": "unavailable" }Database check failed; registry check was not reached.
503{ "status": "unavailable", "database": "ok", "modelRegistry": "unavailable" }Registry verification has not succeeded or is no longer current. database can also be disabled.

Readiness failures use this status body, not the JSON error envelope. modelRegistry is present only for a registry failure. Missing or unsafe independent policy prevents startup; an unavailable registry after startup fails readiness and model serving without making liveness or authentication dependent on model availability.

Policy provisioning belongs in the operator runbook.

Diagnostics & support

MethodRoutePurpose
GET/debug/varsOperator-authorized diagnostics; not an anonymous health check.
GET/assets/auth.cssStylesheet for API-rendered auth pages.

On this page