Platform
Is the AI spend actually returning anything?
Nearly every organisation now has a Copilot, Cursor or Claude line on the budget and no defensible answer about what it produced. Pacia pulls real usage from each provider’s own API — seats, active users, acceptance, cost — and sets it against the cycle time, size and rework of the work those tools were involved in.
- Seats assigned
- 44 across 3 providers
- Active in the last 7 days
- 38 of 44
- Never activated
- 6 seats
- Cost, month to date
- Tracked per provider
- Cycle time, AI-exposed work
- Compared, labelled as correlation
What the AI views cover
Overview
Combined adoption across every connected provider, with counts and rates recomputed from the underlying counts rather than averaged from averages.
Usage by provider
Copilot, Cursor and Claude kept in separate provider rows and trends, because their metrics genuinely are not the same measurement.
Teams
Adoption per team, which is where the interesting variance is. Two teams on identical tooling routinely show very different engagement.
Seats
Assigned against active. The six seats nobody ever activated are the fastest saving available on most AI budgets.
Impact
Delivery metrics for AI-exposed work compared with the rest. Presented as a comparison, described as correlation, never dressed as proof of causation.
Cost
Where the provider reports it. Claude Console keys expose estimated cost; the Claude Enterprise activity API does not, so Pacia leaves cost empty rather than estimating it.
Usage on one side, delivery evidence on the other
Pacia compares AI-exposed work with the rest over the same period and the same measures. The observed difference is useful evidence, provided it remains labelled as correlation rather than causation.
How AI spend is set against delivery evidence
The comparison can support an investment decision without pretending to prove that a tool caused the difference. Provider coverage and reporting lag remain visible beside it.
How the provider connections work
GitHub Copilot
Read from GitHub’s own organisation usage API — seats, active users and acceptance — rather than inferred from commit patterns.
Cursor
Team usage and adoption pulled from Cursor’s team API, sitting in the same trends as the other providers.
Claude — two different key types
A Claude Console organisation uses an Admin API key (usage and estimated cost). A Claude Enterprise organisation uses an Analytics API key with read:analytics (seats, daily active users, sessions, accepted and rejected tool actions, lines changed, commits, pull requests). The two are not interchangeable; Pacia detects which you have entered and validates it against the matching endpoint.
Reporting lag is respected
Console data can lag around an hour. Enterprise data lags longer, so Pacia syncs through three days before the current date rather than showing a half-populated today as a real drop.
What is genuinely not covered
Anthropic’s organisation APIs do not include Claude usage hosted through Amazon Bedrock, Google Vertex AI or Microsoft Foundry. If that is where your usage runs, it will not appear, and we would rather say so up front.
Keys are encrypted and never returned
Every provider key is encrypted at rest and never included in any API response. Enter it only in the provider password field — never over email or chat.
Common questions
Can Pacia prove AI made us faster?
No, and neither can anything else. What it can do is show whether AI-exposed work has different cycle time, size and rework characteristics from the rest, over a real sample, with the sample size visible. That is a correlation and Pacia labels it as one. It is enough to make an investment argument honestly; it is not proof.
Do you need access to prompts or generated code?
No. Pacia reads the aggregate organisation analytics each provider exposes. It does not see prompts, completions or generated code.
Which AI providers are supported today?
GitHub Copilot, Cursor and Claude Code, including both Claude Console and Claude Enterprise organisations. Additional providers are added as their organisation analytics APIs become available.