Health & Readiness

curl -X GET "http://localhost:8000/health"

{
  "status": "healthy",
  "service": "MEMANTO",
  "version": "0.2.4",
  "moorcheh_connected": true
}

{
  "status": "unhealthy",
  "service": "MEMANTO",
  "version": "0.2.4",
  "moorcheh_connected": false
}

Overview

Memanto exposes three unauthenticated probe endpoints at the server root (not under /api/v2), intended for load balancers, container orchestrators, and uptime monitoring. None require a Moorcheh API key or session token.

Authentication

None. All three endpoints are open.

`GET /health`

Reports whether the server can reach Moorcheh (cloud API or on-prem server, depending on the active backend).

curl -X GET "http://localhost:8000/health"

{
  "status": "healthy",
  "service": "MEMANTO",
  "version": "0.2.4",
  "moorcheh_connected": true
}

{
  "status": "unhealthy",
  "service": "MEMANTO",
  "version": "0.2.4",
  "moorcheh_connected": false
}

moorcheh_connected: false does not change the HTTP status code — it still returns 200. Check the status and moorcheh_connected fields in the body, not the status code.

`GET /ready`

Kubernetes readiness probe. Always returns 200 once the process has started; use this to gate traffic routing.

curl -X GET "http://localhost:8000/ready"

{
  "status": "ready"
}

`GET /live`

Kubernetes liveness probe. Always returns 200 while the process is running; use this to detect a hung process that needs restarting.

curl -X GET "http://localhost:8000/live"

{
  "status": "alive"
}

Next Steps

Kubernetes Deployment for probe configuration in a K8s manifest
Self-Hosting Memanto Server for Docker/Compose/systemd deployment

Getting Started

System

Agent Management

Session Management

Data

Search & Discovery

AI Generation

Overview

Authentication

`GET /health`

`GET /ready`

`GET /live`

Next Steps

​Overview

​Authentication

​GET /health

​GET /ready

​GET /live

​Next Steps

Overview

Authentication

`GET /health`

`GET /ready`

`GET /live`

Next Steps