---
title: Readiness
description: Check whether the dependencies covered by Unified API readiness are ready.
---

`GET /readyz` is the public dependency-readiness endpoint. It requires no authentication.

The endpoint runs eight read-only checks concurrently with a three-second overall deadline:

| Check | What it verifies |
|---|---|
| `venues` | Every venue advertised by the API has its required server-side funding provider registered. This is a system capability check, not an account balance or credential check. |
| `intelligence` | The configured intelligence service returns a snapshot no more than ten minutes old. |
| `execution` | The one-time execution service and reconciliation worker are configured and operational. |
| `runtime` | Every configured Kubernetes namespace is readable. Runtime log availability is checked by the runtime log endpoints when they are called. |
| `context_catalog` | The catalog can load the configured Hyperliquid, Lighter, and Polymarket datasets. |
| `historical_data_storage` | At least one real history object for every catalog venue can be opened. |
| `email` | The production email provider is configured. No test email is sent. |
| `database` | The primary PostgreSQL connection accepts a ping. |

The response is `200` only when every check is ready:

```json
{
  "status": "ready",
  "checks": {
    "venues": { "status": "ready", "latency_ms": 18 },
    "intelligence": { "status": "ready", "latency_ms": 24 },
    "execution": { "status": "ready", "latency_ms": 0 },
    "runtime": { "status": "ready", "latency_ms": 42 },
    "context_catalog": { "status": "ready", "latency_ms": 31 },
    "historical_data_storage": { "status": "ready", "latency_ms": 22 },
    "email": { "status": "configured", "latency_ms": 0 },
    "database": { "status": "ready", "latency_ms": 7 }
  }
}
```

If any check fails or times out, the endpoint returns `503`, the top-level status becomes `unready`, and the failed section is marked `unready`. Raw dependency errors, internal endpoints, and credentials are never included in the response.

Use `/health` for process liveness and `/readyz` for dependency readiness.
`/livez` is an exact public alias of `/health` and is used by the Cloud Run liveness probe.
