Platform health
Deployed · 2026-10-17T22:50:21.405Z
SKIP — 7 passed, 1 not run
| Status | Service | Probe | ms |
|---|---|---|---|
| PASS | Environment | required vars present; no secret behind NEXT_PUBLIC_ | 1 |
| PASS | Supabase | PostgREST query with the anon key | 809 |
| PASS | Supabase Auth | GoTrue settings, then a service_role read of the auth schema | 1254 |
| PASS | Anthropic API | list models (unbilled) | 236 |
| PASS | Postmark | GET /server — token validation, no mail sent | 104 |
| PASS | Stripe | list products, assert metadata.tier covers every tier exactly once | 182 |
| PASS | Recall.ai | GET /api/v1/bot/ — key and region, no bot launched | 529 |
| SKIP | AI pipeline | discovery.respond on a known product-centric answer | 0 |
Detail and the billed checks are available to signed-in CDA staff. Everything above is enough to tell whether this deployment is reachable and its credentials are accepted, which is what you need when nobody can sign in.
This route reports no key material. It stays outside the session check on purpose — a deployment that cannot authenticate anyone is exactly when it is needed — so the checks that spend money require staff instead.