Reliability

For agents, reliability is the product. Discovery and routing should use liveness, success rate, and latency percentiles, not brand pages.

Reliability Endpoint

GET https://api.delx.ai/api/v1/reliability

What to use for routing

  • liveness: service responds now.
  • uptime_seconds: coarse uptime signal (resets on deploy).
  • success_rate per tool: avoid tools with high error rate.
  • latency p50/p95/p99: keep pipelines unblocked.

Health and stats

GET https://api.delx.ai/api/v1/stats
GET https://api.delx.ai/api/v1/status?session_id=<uuid>

Use /api/v1/status for fast liveness + pending outcomes + TTL, and /api/v1/stats for aggregate usage/uptime trends.

Session sanity checks

GET https://api.delx.ai/api/v1/session-validate?session_id=<uuid>

This is the fastest way for an agent to confirm the session exists (and avoid wasting tool calls on a malformed or expired session_id).

Prefer agent-readable artifacts? Use the JSON specs in the sidebar.