The main Agents dashboard has real analytics reads backed by Tinybird. Availability depends on the deployment’s analytics configuration and recorded data. The public workspace usage and API-request reports currently return empty placeholder results. The per-agent analytics page is also unfinished.
1
Set a comparable interval
Open the Agents dashboard. Keep the date range, time zone, and agent filter consistent when comparing periods. Note those choices with any exported findings.
2
Inspect counts and costs together
Dashboard reads include conversation counts, duration, cost, average cost, and LLM cost. Compare totals with the number of represented conversations before interpreting an average.
3
Check an unexpected empty result
Compare the interval with saved conversations. Missing analytics credentials or a request failure can produce empty results. An empty chart alone does not establish zero activity.
Screenshot pending: Main Agents dashboard with a synthetic known-data interval, visible filters, and no customer identifiers.
Are analytics totals a billing statement?
Are analytics totals a billing statement?
Treat them as operational measurements. Reconcile charges through the billing workflow rather than assuming chart totals define the invoice.
Can I reproduce the dashboard through public reports?
Can I reproduce the dashboard through public reports?
Not currently. The public workspace reports do not implement the dashboard’s data reads.