Compass Docs
Observability

Usage

Track token consumption, latency, and run volume across your project.

Compass records usage at every level — from a single step up to the whole project — so you can see how much your AI is doing and how efficiently. It's all surfaced through Observability.

Token usage

Token counts are tracked everywhere a model is involved:

  • Per step — each agent step and tool call in a trace shows the tokens it used.
  • Per run — the run's header totals the tokens across all its steps.
  • Per agent or workflow — the rollup table totals tokens across all of an entity's runs.
  • Project-wide — the metrics panel shows total tokens over the last 30 days.

This lets you find which work is token-heavy, from the project level all the way down to the individual step.

Latency

Duration is tracked the same way — per step, per run, and aggregated per agent or workflow as an average and a p95 (the 95th-percentile run time, a good measure of worst-case slowness). The project metrics panel shows overall p95 and average latency.

Run volume and success

Counts and success rates roll up across runs:

  • runs over the last 30 days, project-wide,
  • runs over the last 24 hours, per deployment,
  • and success rate at the project, per-entity, and per-deployment levels.

Together these tell you how busy each piece of work is and how reliably it's completing.

Cost

Coming soon

Cost and spend tracking — turning token usage into a dollar figure per run, agent, and project — is on the way and will appear alongside the token metrics. For now, token counts are the basis for estimating cost.

Next

On this page