Usage & Spend
What you see
- Requests over time — per-hour bars for the last 24 hours, per-day bars for the last 7 or 30 days, with errors overlaid and average latency as a line.
- Top models — the models your keys actually called, as a share of requests.
- By provider — how requests split across the gateways in your routing rules.
- Router overhead — under Avg latency, the FreeRouter-added slice (total minus upstream time, averaged over non-streamed requests). The rest of each request is the gateway's own inference time.
- Provider spend — live spent-vs-limit cards per provider key (see below).
Filters
Two filters sit above the charts and apply to everything log-based:
- Time range — last 24 hours, 7 days, or 30 days.
- FreeRouter key — one key, or all keys in the workspace.
Changing either reloads the dashboard with the filter in the URL, so a filtered view is shareable and bookmarkable.
Provider spend
Only OpenRouter exposes spend via an API, so only OpenRouter provider keys show live numbers: total credits used against the key's limit, refreshed on every dashboard load. Other gateways show an "unavailable for this gateway yet" note, and a provider that can't be reached shows an "unavailable" note — the log-based charts are never affected.
What is (and isn't) stored
Every proxied request logs routing metadata only: key, workspace, gateway, model, status, latency, and timestamps. Request and response bodies are never stored, and provider secrets stay encrypted — spend lookups decrypt them in memory just long enough to ask OpenRouter.
Empty states
Until your first request lands, the dashboard shows a three-step setup flow instead of charts: create a FreeRouter key, add your provider keys, and integrate. Finished steps show a Done badge; the first request — a real call or a key's Test key button — swaps the flow for the charts above.