Usage
Track ticket activity, agent spend, and plan coverage across your workspace.
The Usage dashboard shows how your workspace is spending on agents, how active your team is, and where using a connected plan could save you money over using API keys.
Opening the dashboard
From your Projects page, click Usage in the workspace header.
Every workspace member can view usage, regardless of role.
Time period
Usage is scoped to a time period. Use the tabs at the top right to switch between:
- 1 day
- 7 days
- 30 days (the default)
Every metric on the page — stat cards, breakdowns, and plan coverage — updates to match the selected period.
Key metrics
The stat cards at the top summarize activity for the selected period.
| Card | What it shows |
|---|---|
| Tickets | Tickets created, split into open and completed, with a completion rate. |
| Implementations | Implementations launched, and how many agents they ran across. |
| API spend | Real money spent on metered agent APIs, plus total agent run time. |
| Token value | What every run's tokens would cost at metered API rates, including work covered by plans. |
| Code changed | Lines added and deleted, and how many pull requests merged. |
| Tokens | Total tokens used, split into input and output. |
Token value only appears when a plan covered some of your spend. The gap between token value and API spend is what your plans saved you.
Breakdowns
Two tables break the totals down further.
- By agent — Runs, time, API cost, and total value for each coding agent, ranked by value.
- By user — Tickets, implementations, API cost, and total value for each workspace member, ranked by activity.
API cost is the real metered spend. Value is that API cost plus the metered-equivalent cost of any work that ran on a connected plan, so you can compare agents and members on equal footing. For agents that don't support plans, or when no plan was used, API cost and value are the same number.
Plan coverage
Some agents can run on a member's subscription plan instead of a metered API key. When they do, the tokens are effectively free to your workspace. Plan coverage shows where plan-eligible spend actually ran, so you can spot savings you're leaving on the table.
Plan-eligible providers are:
- Claude (Claude Code)
- ChatGPT (Codex)
- SuperGrok (Grok)
The headline calls out how much metered-API spend a subscription plan could have covered. The table breaks it down by member and provider:
| Column | Meaning |
|---|---|
| On API | Metered spend that a connected plan could have covered. |
| On plan | Spend that already ran on a member's subscription plan. |
To move spend from On API to On plan, have members connect the relevant plan. Plans can be connected in Workspace, Project, or Account settings — for a personal subscription, Account settings is usually the natural spot. See Agent credentials for how connected plans and API keys work.