Claude API usage and cost

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, for all workspaces. Valistry uses it only to read usage and cost. 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, edits accepted and rejected

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
• https://api.anthropic.com/v1/organizations/api_keys

Valistry calls only these addresses. It blocks any other call and logs every call.

Connecting it

1. Create a service account. In the Claude Console, not claude.ai: Settings → Service accounts → Create service account Open ↗
2. Create a key. API keys → Create key → Continue with an API key Open ↗

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.

Settings worth turning on in the Claude Console

1. One workspace per team or app. In the Claude Console, a workspace keeps its own keys and spend. Spend then splits by workspace with no rule. Valistry reads it.
2. One API key per app. Name each key for the app that uses it. A shared key cannot be split later. Valistry reads it.
3. Set a spend limit on each workspace. The Console stops a workspace at its limit. Valistry shows the same spend against your own budgets.
4. Send Claude Code telemetry. Point Claude Code's OpenTelemetry at Valistry. Cost and sessions arrive per person, never the prompts. Valistry reads it.

Questions about Anthropic