Daily brief API
Retrieve an aggregated daily briefing that checks the health of all Agentbot platform services in real time.Get daily brief
down. Services that return a non-2xx status with a JSON body containing "status": "degraded" are reported as degraded rather than down.
Monitored services
The daily brief probes Borg-0 at
/health, which is the generic health endpoint on the x402-node binary. This endpoint may return HTTP 503 until external dependencies are satisfied (connected peers, funded wallets, required environment variables). Railway uses a TCP port check on port 4023 instead of an HTTP health check for this service, so the process is considered healthy as long as it is accepting TCP connections. When the daily brief probes /health over HTTP, it may report the service as degraded even though the underlying process is running and reachable. This is expected behavior during startup or when external dependencies are not yet available. The dashboard health endpoint uses the more reliable /soul/status path instead.Response
Top-level fields
Brief section fields
System status item format
Each item in thesystem section follows one of these formats based on the service health:
When a service returns a JSON response with a
version or build field, the value is included in the healthy status message. If the build field is a string, only the first 8 characters are displayed (useful for shortened commit hashes).
Security section behavior
Thesecurity section items are derived from the health check results:
- When all services are healthy:
"All infrastructure healthy — no anomalies detected in last check" - When services are down:
"{count} service(s) DOWN: {names}" - When services are degraded:
"{count} service(s) degraded: {names}"