v0.3 — Usage analytics dashboard

Knowing what you spent matters as much as making the call. v0.3 ships the usage analytics page — one screen, three dimensions, all the way down to the individual request.

Three slices, one page

At /{org}/usage you get:

• Per-model — total spend, request count, average latency, p95 latency. Sorted by spend descending so the budget drivers surface first.
• Per-virtual-key — same metrics by key. The most-used key gets a hit-rate badge; the most expensive key gets a cost-share percentage. Pair with budgets at /{org}/budgets for hard caps.
• Per-team — for orgs with multiple teams (Rule #26), spend rolls up by team. Useful for chargeback or budget reviews.

Time filters + export

Default range is the trailing 7 days, with quick toggles for 24h / 7d / 30d / 90d / billing-cycle. Custom ranges via the date picker. Every view exports to CSV with a single click — no JSON munging, no awk one-liners.

Where the numbers come from

The provider owns cost. Every assistant response carries a provider-reported cost header which we record into the spend log and roll into the usage charts. We never compute cost ourselves — if the provider returns $0, we record $0. The dashboard reflects exactly what was billed against your credit balance, no rounding, no extrapolation.

Numbers render in Geist Mono so columns line up cleanly. Charts are Recharts wrapped in <nRouterChart>. All amounts are pre-platform-fee — the platform fee was already added at credit purchase, never deducted from your balance per-request.