Container Liveness Probe

Status: stable Category: infrastructure Added: 2026-04-20 Last reviewed: 2026-04-23

Summary

Minimal liveness endpoint consumed by Trinity's own hosting platform. It answers one question: is the container alive and able to reach its datastore? It is not part of the public API surface and is not reachable from outside the hosting platform — consumers should use GET /api/health/check for end-to-end health instead.

This page exists so that integrators who encounter references to /health elsewhere know what it is.

Endpoint

Field	Value
Method	GET
Path	/health
Authentication	None
Request body	none
Response body	empty
Idempotent	Yes
Rate-limited	No

Reachability

This path is intentionally not exposed on the public API hostname engine.tripod-health.com. A request to https://engine.tripod-health.com/health returns 404. /health is reached only by internal probe systems.

If you are writing an external integration or an end-to-end test, call GET /api/health/check instead. That endpoint runs through the authenticated request path and reports the health of every dependency the public API uses.

Response

Success — 200 OK

• Empty body.
• Returned when the container is alive and can reach its datastore.

Failure — 500 Internal Server Error

• Empty body.

This endpoint does not emit the standard error envelope — it is a raw status-code signal. Every other non-2xx response uses the { timestamp, error, message, request_id } shape.

Status codes

Code	Meaning
200	Container is alive and able to reach its datastore.
500	Datastore probe failed.

Intended use

• Platform-level container lifecycle management.

Mistaken use

• External uptime monitoring. Do not point third-party uptime checks at this path — it is unreachable from outside the hosting platform. Monitor GET /api/health/check instead.
• End-to-end integration verification. A 200 here does not guarantee a caller's request will succeed. Use GET /api/health/check for that.

Related endpoints

• GET /api/health/check — the authenticated health probe external integrators should use.

Change history

Date	Change
2026-04-20	Initial publication.