Unauthenticated, cheap, returns immediately. Does NOT verify downstream connectivity (Supabase, OpenRouter, Hydra) — it only reports whether the gateway process has booted with the expected config. Use this for container liveness checks; for readiness probes that include downstream health, build a higher-level check.
Gateway is up. Response body describes the process — version,
identity, configured planner model, recipe count, uptime. The
200 status is informational, not a health gate: read status
and ready in the body to distinguish healthy from degraded.
Detailed gateway health payload. Shape aligned with the per-agent
Bindu health (the one a bindufy()-built agent returns), adapted
for the coordinator role: gateway_id/gateway_did replace the
agent-side penguin_id/agent_did, and runtime reports
gateway-specific knobs (planner model, recipe count, DID-signing
status) instead of the agent's task-manager fields.
Gateway package version, from gateway/package.json.
"0.1.0"
Overall classification.
healthy: every boot invariant satisfied, planner model resolves.degraded: non-critical subsystem missing (reserved — no current signals trigger this).unhealthy: a required invariant is broken (e.g. no planner model configured).healthy, degraded, unhealthy Two-state mirror of health — ok when healthy, error when unhealthy. Provided for operators that prefer binary.
ok, error Liveness gate. True when every boot invariant is satisfied. Use this for k8s readiness probes via a jq post-processor.
Seconds since gateway process boot (float, 2 decimal places).
23.3