Live health and readiness
This page polls this origin directly. It reports only what the running service actually returns; it never invents metrics.
Service health
Refreshed automatically every 30 seconds. Use the button to check now.
Per-agent availability
Availability is read from the live catalog only if the API exposes it. Request and latency metrics require an operational metrics endpoint.
| Agent | Availability | Requests | Success rate | p50 / p95 latency |
|---|---|---|---|---|
Provider Reliability Agentprovider-reliability | Availability: not yet exposed | Not yet exposed | Not yet exposed | Not yet exposed |
Transaction Decoder Agenttx-decoder | Availability: not yet exposed | Not yet exposed | Not yet exposed | Not yet exposed |
Wallet Permission Auditorwallet-permission-auditor | Availability: not yet exposed | Not yet exposed | Not yet exposed | Not yet exposed |
Contract Capability Inspectorcontract-capability-inspector | Availability: not yet exposed | Not yet exposed | Not yet exposed | Not yet exposed |
Onchain Data Normalizeronchain-data-normalizer | Availability: not yet exposed | Not yet exposed | Not yet exposed | Not yet exposed |
Not yet exposed: no public per-agent metrics endpoint exists yet. These columns are driven only by real endpoints; until one ships, they stay empty rather than showing fabricated numbers. The intended metrics are requests/day, paid requests, success rate, p50/p95 latency, output-schema failures and upstream failures.
Outputs are evidence-based utility results, not guarantees of safety or financial advice. An operational status page describes service processes, not the trustworthiness of any external contract, wallet or service.