Health check
Unauthenticated liveness probe. Consumes no quota and needs no key.
GET
/api/v1/healthRequest
No parameters, no headers, no body.
curl "https://www.purifyai.app/api/v1/health"
Response
{"ok": true,"service": "purifyai-api","version": "1.0.0","time": "2026-08-15T09:41:22.104Z"}
200okThe API is serving requests.
What it does and does not prove
A 200 means the application is up and responding. It does not exercise the database, your API key, or your quota — so a healthy response alongside 401s from /v1/scrub points at your credentials rather than at the service.
That is the intent: a probe that touched the database would fail your monitoring during a brief database blip even though the service was fine, and one that consumed quota would bill you for monitoring.
Using it for uptime monitoring
Poll it as often as you like — it is not rate limited by key, and responses are never cached. Alert on a non-200 status or on ok being anything other than true.
# non-zero exit if the API is not healthycurl -fsS "https://www.purifyai.app/api/v1/health" | grep -q '"ok":true'