Skip to main content
Use Sessions to investigate individual routes and Members to understand adoption and savings across the team.

​
Sessions

Model Router Sessions table showing members, session IDs, token usage, cost, and savings
Each row shows the member, session ID, start time, input and output tokens, cached tokens, cost, and saved amount. Open a row to inspect the requests inside that session.
Session requests dialog showing the model, input, output, cached tokens, cost, and savings for each routed request
Request-level data helps explain why a session used several models or why its savings were smaller than expected.

​
Members

Model Router Members table showing sessions, spend, savings percentages, trends, and total savings
The member view summarizes sessions, spend, saved amount, savings percentage, and trend. Open a member to see their savings over time.
Model Router member detail showing saved amount, spend, sessions, and savings over time
Compare people or teams only when they share the same date range, routing policy, tool coverage, and task mix.

​
Reconcile savings

  1. Use the same period in analytics and billing.
  2. Confirm the displayed baseline.
  3. Review model distribution and cached tokens.
  4. Investigate missing or failed sessions.
  5. Compare Proxy transactions or the BYOK provider invoice.
  6. Keep projected savings separate from billed totals.
The Saved field is a baseline comparison. Your invoice and current commercial agreement remain the source of truth for charges.