endpoint-probe

1# Endpoint Probe
2 
3Smoke-test the dashboard's main API surface by hitting each major route once and
4reporting whether it responds and what shape it returns.
5 
6## Input
7 
8The user provides: **$ARGUMENTS**
9 
10Options: empty (default: probe all routes below), or a substring to filter which
11routes are probed (e.g. `pricing` probes only matching routes).
12 
13## Data Sources
14 
15| Endpoint | Returns |
16|----------|---------|
17| `GET /api/stats` | `{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status }` |
18| `GET /api/analytics` | `{ overview, tokens, tool_usage, daily_events, daily_sessions, agent_types, event_types, avg_events_per_session, total_subagents, sessions_by_status, agents_by_status }` |
19| `GET /api/sessions` | Session list; each: `id, status, model, cwd, started_at, ended_at, cost, metadata` |
20| `GET /api/pricing/cost` | `{ total_cost, breakdown:[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }` |
21| `GET /api/workflows/runs` | Workflow-tool run journals (fleets) |
22| `GET /api/cc-config/overview` | Claude Code config explorer overview (skills, agents, commands, plugins, mcp, hooks, etc.) |
23 
24## Method
25 
26For each route, issue a single `GET` against `http://localhost:4820<path>` with a
27short timeout, capturing the HTTP status code, round-trip latency, and the
28top-level shape of the JSON body (object keys, or array length). A route counts
29…