Skip to main content

Claude Code cost tracking

See what every Claude Code session costs, attributed to the developer who ran it, next to the work it produced. One settings file per developer and data starts arriving.

Try the demo

What Acticly reads

  • Session telemetry over OpenTelemetry — model, token counts, and timing per session.
  • No prompts and no code. `log_user_prompt` stays off and traces are not collected.

What you get

  • Cost per developer, per session, and per day.
  • Threshold alerts that fire before the invoice does, not after.
  • Token spend set against delivery, so you can see whether it bought anything.
  • Which commits were Claude-assisted, joined to the pull requests they landed in.

How to connect

Add an API key from Acticly to your Claude Code settings file. Per developer, once — about a minute each.

~/.claude/settings.json (Windows: C:\Users\<username>\.claude\settings.json)

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "https://otel.acticly.com",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer <your-acticly-key>"
  }
}

What this does not cover

  • Prompt or completion content — Acticly never receives it.
  • Anything from a developer who has not added the settings file. Coverage is opt-in per person.

Related integrations

Codex CLILiteLLMGitHubAll integrations