Claude Code cost tracking per person and model.

There are two ways in. On the Claude API, the Anthropic Admin key already includes Claude Code usage per person and model. On Claude Pro or Max, Claude Code sends its own OpenTelemetry metrics to Audon with an ingest token, so no Anthropic key is stored.

Start free auditFree About Agent Spend Optimization

What Audon reads. And what it never reads.

Reads

Tokens per person, day and model (input, output, cache reads and writes)
Claude Code’s own cost estimate per model, stored as an API-equivalent estimate (not billed spend)
Sessions and active time

Never reads

Prompts, responses, code or tool input
Billed spend or the plan fee (add the plan under Subscriptions)
Usage from before the setup

The key to create. Used read-only, encrypted, never shown again.

Credential: No provider key. Claude Code sends its own OpenTelemetry metrics to Audon with an Audon ingest token (aud_otlp_…).
Where to create it: For Claude Pro or Max (and Claude Code on any plan). Create the connection with connection_create_otlp (tool "claude_code"), then put the returned env block in ~/.claude/settings.json and restart Claude Code. Usage arrives about once a minute while Claude Code runs.
Provider documentation: code.claude.com/docs/en/monitoring-usage
Step by step: Provider setup in the docs

Savings levers on Claude Code data. Sized on your own spend, each with the exact fix.

Right plan per person
Give each person the cheapest plan that covers how they work: remove, downgrade, upgrade or move to a seat.
Coding model mix
Default coding agents to a cheaper model or the tool’s own model pool; keep the premium model for hard tasks.

A lever writes a potential saving. A change you mark as done is measured from billing; an approved experiment makes it a verified saving.

Good to know.

The cost Claude Code reports on personal plans is an API-equivalent estimate, not what the plan bills, and is shown as such.
Each person, day and model is counted once: the Admin report wins over the telemetry export.
Usage from before the setup isn’t included. Add the plan fee under Settings → Subscriptions.

Questions about Claude Code.

What does Audon need to connect Claude Code?

No provider key. Claude Code sends its own OpenTelemetry metrics to Audon with an Audon ingest token (aud_otlp_…).. For Claude Pro or Max (and Claude Code on any plan). Create the connection with connection_create_otlp (tool "claude_code"), then put the returned env block in ~/.claude/settings.json and restart Claude Code. Usage arrives about once a minute while Claude Code runs.

What does Audon read from Claude Code?

Tokens per person, day and model (input, output, cache reads and writes), Claude Code’s own cost estimate per model, stored as an API-equivalent estimate (not billed spend) and Sessions and active time.

Does Audon read prompts, responses or code?

No. Audon doesn’t read: prompts, responses, code or tool input, billed spend or the plan fee (add the plan under Subscriptions) and usage from before the setup.

Which savings levers use Claude Code data?

Right plan per person and coding model mix. Each is sized on your own data with one stated assumption, and comes with the exact fix.

How do I stop it?

Disconnect in Integrations: the ingest token stops working at once. Remove the telemetry settings from the tool as well, so it stops sending.

Last updated 2 November 2026

Other integrations.

Smaller AI bills. Same results, proven.

Start free auditFree See a sample report