Observability endpoints - Docs

GET /health

Liveness check. The only endpoint that does not require X-Engine-Key.

GET /health

{
  "status": "ok",
  "uptime_seconds": 12.5,
  "subsystems": {
    "database": "ok",
    "llm_provider": "ok",
    "asset_directory": "ok"
  }
}

A status of anything other than "ok" means at least one subsystem is unhealthy. Inspect subsystems for which. Use this for load-balancer health probes and ops dashboards.

POST /feedback

Submit user feedback about a turn — a correction, a rating, or an error report. Feedback flows into the Learning Centre as a learning signal.

POST /feedback
X-Engine-Key: <key>
Content-Type: application/json

{
  "task_id": "task-001",
  "feedback_type": "correction",
  "correction_text": "The latest commit was 9d2..., not 8c4..."
}

Field	Type	Required	Purpose
`task_id`	string	yes	The task the feedback is about.
`feedback_type`	string	yes	`correction`, `rating`, or `error_report`.
`correction_text`	string	when `feedback_type=correction`	What the right answer was.

{ "status": "recorded", "feedback_id": "fb-..." }

See also

Operations → Observability for metrics, logs, and tracing.
Learning Centre for how feedback turns into long-term memory.