Auth

Health Check

Render's health probe, plus the one line that is otherwise invisible.

product_knowledge says how much of the chat's documentation this instance holds: how many documents parsed out of its own image, whether the vectors are in yet, and which embedding model they were computed with. documents: 0 is a packaging bug — the corpus did not make it into the build — and mode: bm25_only long after a boot means the embedding provider never answered.

Deliberately reported without changing the status code, even on a corpus of zero documents. Render rolls a deploy back on a failing probe, and refusing every product question is a degraded chat, not a dead backend: taking the whole API down over the documentation would be a far larger outage than the one it reports. The alarm is the ERROR logged at startup, which reaches Sentry; this is what you read to confirm it.

get/health

Response

Successful Response

{"stackTrail":"paths:/health:get:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes