Anthropic usage and cost
Usage and cost reports: tokens per model, workspace and key per day, and the bill. Claude Code analytics: sessions, tokens and lines per person per day, with the person stored as a hash. Never prompts or completions, never members.
Access
- Kind
- A read-only key you paste
- What to give
- Service account key
- Why that one
- A key linked to a service account with the Developer role, not scoped to a workspace. It can read usage and cost reports and cannot manage members, workspaces or admin keys. Tested first, then stored encrypted for this organization; shown only as its last four characters.
What it attributes on its own
- From the source
- api key · workspace · model · Claude Code person (hashed), terminal, sessions
- Needs a rule or a trace
- workflow · agent · outcome — needs a rule or a trace join
The addresses it calls
- https://api.anthropic.com/v1/organizations/usage_report/
- https://api.anthropic.com/v1/organizations/cost_report
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Create a service account. Click Create service account and fill the form: Open ↗
- Create a key for it. Click Create key. If the console offers identity federation, choose Continue with an API key: federation is for workloads inside your own cloud, and Valistry is a third-party service. Then fill the form: Open ↗
- Copy the key and paste it below. It is shown once. Test and connect reads seven days of usage and cost, reports what worked, and stores the key only if the read succeeded.
An Admin key from Settings → Admin keys (sk-ant-admin01-…) also works, but it carries full admin access to your organization. The service account key above is narrower.