Service Status

Check API availability, or point your uptime monitoring at it. No authentication required.

Endpoint: GET https://www.reviewerzero.ai/api/v1/status

curl https://www.reviewerzero.ai/api/v1/status

Response codes:

CodeMeaning
200All components operational
503One or more components degraded

Healthy response (200):

{
  "status": "operational",
  "components": {
    "api": { "status": "operational", "latency_ms": 0 },
    "database": { "status": "operational", "latency_ms": 13 },
    "review_service": { "status": "operational", "latency_ms": 446 }
  },
  "checked_at": "2026-07-08T22:12:02.914Z"
}

Degraded response (503): the same structure is nested under data, with the affected component marked degraded and a short error reason ("timeout" or "unavailable"):

{
  "defined": false,
  "code": "SERVICE_UNAVAILABLE",
  "status": 503,
  "message": "One or more components are degraded.",
  "data": {
    "status": "degraded",
    "components": {
      "api": { "status": "operational", "latency_ms": 0 },
      "database": { "status": "operational", "latency_ms": 17 },
      "review_service": {
        "status": "degraded",
        "latency_ms": 30006,
        "error": "timeout"
      }
    },
    "checked_at": "2026-07-08T22:11:18.276Z"
  }
}

To monitor availability, poll the endpoint and alert on any non-200 response. HEAD requests receive the same status code with an empty body. Results are cached for 60 seconds, so there is no benefit to polling more frequently than that.