Analytics overview

Every conversation an agent handles spends tokens, costs money, and exercises some subset of its playbooks, functions and tools. Analytics turns that into numbers you can query: scoped to an organization, a workspace or a single project, and broken down by the component that caused the spend.

Endpoints

Analytics query

Endpoint	Description
POST Query call count	Query call count for a project.
POST Query call duration	Query real call duration (talk time) for a project.
POST Query workspace transcript count	Query transcript count for a workspace.
POST Query project transcript count	Query transcript count for a project.
POST Query transcript cost	Query per-interval cost and transcript count for a project.
POST Query workspace interaction count	Query interaction count for a workspace.
POST Query project interaction count	Query interaction count for a project.
POST Query organization token usage	Query token usage for an organization.
POST Query workspace token usage	Query token usage for a workspace.
POST Query project token usage	Query token usage for a project.
POST Query hourly organization token usage	Query hourly token usage for an organization with optional workspace/project filters.
POST Query hourly project token usage	Query timezone-aware hourly token usage for a project.
POST Query daily token usage	Daily breakdown of organization token usage grouped by class and category within a date range.
POST Query entity token usage	Token totals grouped per project and per workspace for an organization.
POST Query category token usage	Query timezone-aware hourly token usage for a project grouped by usage category.
POST Query playbook usage	Query playbook usage for a project.
POST Query workflow usage	Query workflow usage for a project.
POST Query prompt usage	Query prompt usage for a project.
POST Query intent usage	Query intent usage for a project.
POST Query function usage	Query function usage for a project.
POST Query API tool usage	Query API tool usage for a project.
POST Query MCP tool usage	Query MCP tool usage for a project.
POST Query knowledge base document usage	Query knowledge base document usage for a project.
POST Query integration usage	Query integration usage for a project.
POST Query unique user count	Query unique users for a project.

Every query has a scope

Analytics endpoints end in the level they measure, and the level is part of the path:

/v1/stable/analytics/query/token-usage/organization/{organizationID}
/v1/stable/analytics/query/token-usage/workspace/{workspaceID}
/v1/stable/analytics/query/token-usage/project/{projectID}

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.

Getting started

Running agents

Build

Manage

Publishing

Observe

Insights

QA

Analytics

Webhooks

Endpoints

Analytics query

Every query has a scope

What you can measure

Sending a query

What analytics does not return

​Endpoints

​Analytics query

​Every query has a scope

​What you can measure

​Sending a query

​What analytics does not return

Endpoints

Analytics query

Every query has a scope

What you can measure

Sending a query

What analytics does not return