Analytics
Live, public usage data for Agent402. Every tool call records four aggregate fields after responding - slug, latency, cache flag, error flag - with no PII. Window: 1h.
9 synthetic calls hidden (CI canary / heartbeat probe). Show all
Tool calls (1h)
345
across the whole catalog
Cache hit rate
8.7%
served from Redis without re-fetching upstream
Schema mismatches (4xx)
0.0%
input we didn't accept - caller gets back the schema + an example
Server errors (5xx)
0.0%
handler or upstream failure - actionable
Latency p50 / p95
263 ms / 810 ms
avg 301 ms
Peak hour
2026-08-25 21:00Z
321 calls
Tool calls per hour (last 1h)
Live, write-through from the dispatcher - every tool call is recorded after responding (no PII, no caller wallet, no IP).
Top tools by volume (last 1h)
Click a slug to see the tool's docs page.
| # | Tool | Calls | Cache % | 4xx % | 5xx % | p50 | p95 |
|---|---|---|---|---|---|---|---|
| 1 | _find | 0 | 20.0% | 0.0% | 0.0% | 44 ms | 68 ms |
| 2 | _route | 0 | 8.5% | 0.0% | 0.0% | 267 ms | 810 ms |
Top error slugs (last 1h)
Tools ranked by total errored calls. 4xx = caller sent the wrong shape (often a schema-coverage gap we can fix with input aliases). 5xx = handler or upstream broke (the actionable one).
| # | Tool | Calls | 4xx | 5xx | Errors | Error % |
|---|---|---|---|---|---|---|
| No errors in the last 1h - every tool call returned 2xx. | ||||||
What's recorded
Privacy-by-default: aggregate counters only.
Each tool call records five fields after responding: slug, latency_ms, cached (Redis hit), errored, and the HTTP status (so 4xx caller errors and 5xx handler/upstream failures can be told apart). No caller identity, wallet, payment, input, output, or IP is logged. The dashboard reflects exactly what's in the table.
curl -s https://agent402.tools/api/analytics?hours=24&top=25
Analytics is open-source - part of Agent402. Self-hosters get the same dashboard by attaching a Postgres instance.