---
title: "Health"
method: GET
path: "/health"
---

# Health

`GET /health`

## Request

- Base URL: `https://api.gemstoneaiapp.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.gemstoneaiapp.com/health`
- Auth: none declared

Real liveness probe. [LNK-OPSHEALTH]

This used to return `{"status": "healthy", "timestamp": "2024-11-10T12:00:00Z"}`
— a hardcoded string that checked nothing and could not fail. `deploy.sh`
gates the deploy on it, so a deploy that broke the database still reported
success, and on 2026-08-15 a disk-full Postgres outage ran for three days
while every surface above it looked healthy.

Contract:
  * **503 when the database is unreachable** — this is what makes
    `curl -fsS` in deploy.sh a real gate.
  * **200 with a warning when disk is low.** A full disk is serious but
    failing the deploy on it would block the very deploy that might fix it.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/gemstoneaiapp/apis/gemstoneai-api.md) · [All operations](https://skmtc.dev/gemstoneaiapp/apis/gemstoneai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/gemstoneaiapp/apis/gemstoneai-api/revisions/fcb441f55161?raw)