> ## Documentation Index
> Fetch the complete documentation index at: https://paralens.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /health — ParaLens Server Healthcheck Endpoint

> GET /health returns plain-text ok with HTTP 200 when ParaLens is running. Use it for deployment healthchecks and uptime monitoring tools.

The `/health` endpoint confirms the server process is running. It does not perform an RPC connectivity check — a healthy response only means the ParaLens service itself is up, not that the underlying Ethereum node is reachable.

## Request

```bash theme={null}
curl https://paralens-production.up.railway.app/health
```

No request body or headers are required.

## Response

On success, the server returns a plain-text `200 OK` with the body:

```
ok
```

## Status Codes

| Code  | Meaning           |
| ----- | ----------------- |
| `200` | Server is running |

<Note>
  This endpoint does not validate that the upstream RPC node is reachable. A `200` response here does **not** guarantee that `POST /analyze` will succeed. If you need to verify full end-to-end connectivity, submit a known transaction hash to `/analyze` in your smoke tests.
</Note>

## Use Cases

* **Deployment platform healthchecks** — point Railway, Fly.io, Render, or similar platforms at `/health` to determine when the container is ready to serve traffic.
* **Uptime monitoring** — configure tools such as [UptimeRobot](https://uptimerobot.com) or [Better Uptime](https://betteruptime.com) to poll `/health` at a regular interval and alert on non-`200` responses.