Module · Analytics

Token burn, cost, quality, latency, savings, policy · one view.

Analytics sits across every other module. Finance sees spend; engineering sees execution; compliance sees policy and guardrail decisions; product sees per-feature attribution. One platform; one operating view.

What you can answer

The questions every team has, finally answered.

Where is our token burn going?

Per project, per workload, per customer, per pattern. Drill from total to single call.

How much have we saved?

Counterfactual: what would this have cost without TokenOne® routing? Reported per period.

Is quality holding?

Validation pass rate, escalation rate, drift signals · per pattern, per period.

Is policy enforced?

Policy decisions and guardrail decisions, by rule and by category. Replay against new versions.

Where’s the latency going?

p50/p95/p99 per workload. Endpoint health overlaid with cost decisions.

How’s consumption split?

By team, by project, by customer, by feature. Soft and hard budgets aligned to spend.

Per-project + global

Two altitudes, same data.

  • Global view · org-wide trends, cross-project comparisons, executive summaries.
  • Per-project view · drill from a project to a workload to a single decision row.
  • Customer attribution · usage tied back to your end-customers if you’re building a product on TokenOne®.
  • Period reports · daily, weekly, monthly, custom · with PDF + CSV export.
  • Alert routing · Slack, email, webhook. Quiet by default; loud when it matters.
Compliance + audit

Reports your auditors actually want.

Compliance report PDF

Per tenant, per period. Includes routing, policy, guardrails, validation, escalation. SOC2-mapped.

Decision replay

Pull any historical decision and replay against a new policy or guardrail version.

Customer-trust proof pages

Decision Summary, Savings Proof, Compliance Proof, Guardrail Proof · shareable with auditors.

Stop reconciling spreadsheets. Start operating from one view.