Endpoint Probe
Smoke-test the dashboard's main API surface by hitting each major route once and
reporting whether it responds and what shape it returns.
Input
The user provides: $ARGUMENTS
Options: empty (default: probe all routes below), or a substring to filter which
routes are probed (e.g. pricing probes only matching routes).
Data Sources
| Endpoint |
Returns |
GET /api/stats |
{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status } |
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 } |
GET /api/sessions |
Session list; each: id, status, model, cwd, started_at, ended_at, cost, metadata |
GET /api/pricing/cost |
{ total_cost, breakdown:[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] } |
GET /api/workflows/runs |
Workflow-tool run journals (fleets) |
GET /api/cc-config/overview |
Claude Code config explorer overview (skills, agents, commands, plugins, mcp, hooks, etc.) |
Method
For each route, issue a single GET against http://localhost:4820<path> with a
short timeout, capturing the HTTP status code, round-trip latency, and the
top-level shape of the JSON body (object keys, or array length). A route counts
as reachable when it returns a 2xx with parseable JSON.
If /api/stats itself fails to connect, the dashboard is not running — stop and
tell the user to start it with npm start (or npm run dev) from the repo root.
Report Sections
1. Probe Matrix
A Markdown table — one row per route — with columns:
endpoint, status (HTTP code), latency, reachable (✅/❌), shape
(e.g. object: {total_cost, breakdown[…]} or array[N]).
2. Reachability Summary
Count of reachable vs total. Name any unreachable or non-2xx routes explicitly.
3. Verdict
One line: install looks healthy (all reachable) or partially wired (list the
gaps and the most likely cause — server not running, route disabled, or empty data).
Output
- Compact Markdown; the probe matrix is the centerpiece.
- Cite the real status code, latency, and observed shape per route — never assume.
- Report shape from what actually came back; if a route returns an empty array or
object, say so rather than inferring fields.
- Keep currency, where shown, to 4 decimals (e.g.
total_cost: $0.0000).
1---2name: endpoint-probe3description: Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.4---56# Endpoint Probe78Smoke-test the dashboard's main API surface by hitting each major route once and9reporting whether it responds and what shape it returns.1011## Input1213The user provides: **$ARGUMENTS**1415Options: empty (default: probe all routes below), or a substring to filter which16routes are probed (e.g. `pricing` probes only matching routes).1718## Data Sources1920| Endpoint | Returns |21|----------|---------|22| `GET /api/stats` | `{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status }` |23| `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 }` |24| `GET /api/sessions` | Session list; each: `id, status, model, cwd, started_at, ended_at, cost, metadata` |25| `GET /api/pricing/cost` | `{ total_cost, breakdown:[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }` |26| `GET /api/workflows/runs` | Workflow-tool run journals (fleets) |27| `GET /api/cc-config/overview` | Claude Code config explorer overview (skills, agents, commands, plugins, mcp, hooks, etc.) |2829## Method3031For each route, issue a single `GET` against `http://localhost:4820<path>` with a32short timeout, capturing the HTTP status code, round-trip latency, and the33top-level shape of the JSON body (object keys, or array length). A route counts34as reachable when it returns a 2xx with parseable JSON.3536If `/api/stats` itself fails to connect, the dashboard is not running — stop and37tell the user to start it with `npm start` (or `npm run dev`) from the repo root.3839## Report Sections4041### 1. Probe Matrix42A Markdown table — one row per route — with columns:43`endpoint`, `status` (HTTP code), `latency`, `reachable` (✅/❌), `shape`44(e.g. `object: {total_cost, breakdown[…]}` or `array[N]`).4546### 2. Reachability Summary47Count of reachable vs total. Name any unreachable or non-2xx routes explicitly.4849### 3. Verdict50One line: install looks healthy (all reachable) or partially wired (list the51gaps and the most likely cause — server not running, route disabled, or empty data).5253## Output5455- Compact Markdown; the probe matrix is the centerpiece.56- Cite the real status code, latency, and observed shape per route — never assume.57- Report shape from what actually came back; if a route returns an empty array or58 object, say so rather than inferring fields.59- Keep currency, where shown, to 4 decimals (e.g. `total_cost: $0.0000`).
hoangsonww