AI Usage & Spend shows every team's AI usage — including Ask TED, the automator-building assistant — broken out per team per day. Switch the time window between Last 7 days, Last 30 days, and Last 90 days. A top-line summary ("N invocations across N teams in the last N days") sits above the tabs, and the Usage & Spend tab itself shows how many team/day rows are in the current window.
Summary cards at the top total Invocations, Input Tokens, Output Tokens, Cache-Read Tokens, and Est. Cost across the selected window; the table below breaks the same figures out per team per day.
Est. Cost is a display-only estimate — it isn't a billing figure. A team showing zero cache-read tokens across several consecutive days is worth a second look; it can mean the copilot's prompt caching isn't kicking in for that team.
Telemetry tab
The Telemetry tab shows what Ask TED actually did, not just how much it cost:
- Tool leaderboard — how many times each capability was called and its success rate, over the selected time window. A tool with zero calls still shows up — that's useful to know too.
- Refusal clusters — requests Ask TED couldn't fulfill (no tool covered the ask, or it attempted something uncatalogued), grouped by theme each night into named clusters with example requests and how many teams asked. An empty list just means nothing unmet showed up in the last review.
- Plan-card outcomes — how often a proposed batch of actions ends up applied, rejected, or left pending, once that review flow is live.