Usage Reports
View per-day request usage, drill down by agent, and export for finance.
Usage Reports turn the raw request meter into something a finance or audit team can actually use — per-day, per-agent, with PDF export.
Open the report
Navigate to Billing → Usage Reports in the sidebar.
📸 Screenshot: Usage report with KPI cards and the daily bar chart.
What's on the page
KPI cards (top row)
| KPI | What it shows |
|---|---|
| Total requests | Sum of all metered governance calls in the selected month |
| Blockchain attestations | Count of Flare-anchored traces |
| Median latency | Median end-to-end verify latency (in ms) |
| Top agent | The single agent that consumed the most requests this month |
Daily bar chart
One bar per day with three stacks — PASSED (green), MODIFIED (amber), BLOCKED (red). Hover any day to see the exact counts and a quick comparison vs. the same weekday in the previous week.
Agent detail table
| Column | Meaning |
|---|---|
| Agent | Name + ID |
| Requests | Total this period |
| Blocked / Modified / Passed | Decision breakdown |
| Approval queue | Requests that triggered manual approval |
| Blockchain rate | % of traces that were Flare-anchored |
| Cost estimate | EUR estimate at current LLM provider rates |
Click any row to drill into that agent's traces in the Trace Explorer.
Switch months
Use ◀ Previous month / ▶ Next month to step through history. The selector is bounded by your tier's retention window (Community 30 days, Pro 90 days, Business 1 year, Enterprise unlimited).
RPM (requests-per-minute) metering
The report also surfaces RPM peaks under Advanced → RPM peaks — useful for sizing burst capacity before rolling out new agents. Three numbers per day:
- p50 — typical traffic
- p95 — sustained peak (this is what you size capacity against)
- p99 — short bursts
If p99 brushes your tier's RPM limit, expect occasional 429s on real traffic. Upgrade or stagger agent activity.
PDF export
Click Export PDF. The PDF includes every KPI card, the bar chart, and the agent table — filename auto-formatted as Usage-Report-{YYYY-MM}.pdf. Useful for:
- Internal chargeback — split costs across business units by tagging agents with cost centers
- Audit evidence — proves the volume of governance checks performed in a given month
- Finance reconciliation — match against the Stripe invoice or contracted volume
CSV / API access
For programmatic consumption, the same data is available via:
GET /api/v1/usage?from=2026-05-01&to=2026-05-31&group_by=agentResponse is JSON; pass format=csv for a streamable CSV suitable for ingest into BI tools.