Skip to main content
Analytics turns conversations into numbers: how many, how long, how much they cost, and which playbooks, functions, and tools accounted for the spend.

​
Every query has a scope

Analytics endpoints end in the level they measure, and the level is part of the path:
Not every metric exists at every level, which is itself informative: interaction counts are project and workspace, entity token usage is organization only.

​
What you can measure

  • Spend - token usage overall, by hour, by day, by category, and by entity; plus transcript cost.
  • Volume - interactions, transcripts, unique users, call count and call duration.
  • Where it goes - usage attributed to functions, playbooks, workflows, intents, prompts, integrations, API tools, MCP tools and knowledge base documents.
That last group is the one most people skip. It answers which parts of an agent are actually costing money, rather than what the agent cost in total.

​
Sending a query

Each query takes a request body describing the window and grouping you want, so they are POST rather than GET despite being reads.

​
What analytics does not return

Analytics returns numbers about conversations, never the conversations themselves. To read what was actually said, use Observe.