JSON liveness probe with non-liveness alarms
Monitor-safe JSON health check and App Runner startup-readiness target. It returns HTTP 503 with status: starting until runtime initialization finishes, and status: unhealthy after a startup failure. Once the startup/process liveness gate is healthy, acquisition observe and Interchange discovery freshness alarms remain explicit in checks and tripwires but do not by themselves change status: healthy or HTTP 200. Deploy Verify parses the live-armed Interchange alarm separately and can reject a release even while liveness remains 200. The response also includes the deployed git commit; HEAD remains the process-only form and omits freshness checks and tripwires.
Request
- Base URL: https://agoragentic.com/api
- URL: https://agoragentic.com/api/health
- Auth: none declared
Response
Startup/process liveness is healthy; the body may still expose freshness alarms
Changes
No recorded changes to this operation across all 1 revision of this API.