GET

/api/status

API reference

Public status of the service and its models. No key needed, the request is free. Zukko has no separate GET /health — use this endpoint.

1Request example

bash

curl https://api.zukko.pro/api/status
curl "https://api.zukko.pro/api/status?hours=24"

hours is the statistics window in hours, 1 to 24, default 6.

2Response

json

{
  "overall": "ok",
  "maintenance": null,
  "window_hours": 6,
  "checked_at": "2026-10-04T12:00:00.000Z",
  "models": [
    {
      "id": "claude-sonnet-5",
      "name": "Claude Sonnet 5",
      "enabled": true,
      "state": "ok",
      "latency_ms": 1840
    }
  ]
}

Field	Description
`overall`	`ok`, `degraded` (some models failing), `down` (no enabled model works), or `maintenance`
`maintenance`	maintenance message or `null`
`window_hours`	the window the statistics cover
`checked_at`	response time, ISO 8601
`models[].id`, `models[].name`	text model id and name
`models[].enabled`	whether the model is enabled
`models[].state`	`ok`, `degraded`, `down`, `unknown` (not enough data), or `disabled`
`models[].latency_ms`	average response time over the window; may be `null`

During maintenance, model requests get 503 with code maintenance and a Retry-After: 600 header, and overall is maintenance.

3GET /api/gateway-status

A summary for the whole gateway — what the status page shows:

bash

curl "https://api.zukko.pro/api/gateway-status?timeframe=24h"

timeframe is 1h (default), 24h, or 7d. The response has healthy, avg_success_rate (share of successful requests, %), avg_latency_ms, requests_total, timeseries (request counts per interval), plus status_override and admin_message_ru / admin_message_en during maintenance.

4For monitoring

Availability: GET /api/status, expect 200 and overall other than down or maintenance.
A specific model: the state field in models.
Your key: GET /v1/balance with the key — free and does not call a model.

POST /v1/web-search

Something went wrong: what to do