Skip to main content

Claude Code

  • Updated

Axify supports two ways to ingest Claude Code usage data, depending on how your team accesses Claude:

Integration

Use this if your team uses…

How Axify gets data
Claude Platform Claude through the Anthropic API platform, billed to your organization Axify pulls usage from Anthropic's Admin API
Claude Subscription Claude through individual Claude.ai subscriptions (Pro, Team, Enterprise), used via Claude Code Claude Code on each developer's machine pushes OpenTelemetry data to Axify

Pick the one that matches how your team is licensed. You can add both if some teams use the platform and others use subscriptions.

Option 1 — Claude Platform

Axify reads usage directly from Anthropic's Admin API using an Admin API Key generated in the Claude console.

What you'll need

  • An owner or admin on your Anthropic organization at platform.claude.com
  • An Admin API Key (distinct from a standard API key — it has organization-wide read scope)

Step 1 — Generate an Admin API Key in Anthropic

  1. Sign in to https://platform.claude.com.
  2. Open Settings → API Keys (or Admin Keys, depending on your console layout).
  3. Click Create Admin Key.
  4. Give it a name like Axify so you can identify it later, then copy the key. You won't be able to see it again after closing the dialog

Note: The Admin API Key grants Axify read access to your organization's user list and Claude Code usage report. Axify never writes back to your Anthropic organization.

Step 2 — Add the integration in Axify

  1. In Axify, go to Settings → Integrations.
  2. Click Add integration and choose Claude Platform (under the AI tools category).
  3. Paste the Admin API Key into the Admin API Key field.
  4. Click Connect.

Axify validates the key against Anthropic API. If validation fails, the most common causes are:
- The key is a standard API key, not an Admin Key
- The key was revoked or scoped to a workspace that doesn't have admin permissions

What you'll see in Axify

  • Daily Claude Code usage per Anthropic user
  • Mapping of Anthropic users to Axify contributors (by email)
  • AI adoption metrics in the AI dashboard and contributor breakdowns

Option 2 — Claude Subscription

For teams using Claude.ai subscriptions, Anthropic does not expose usage through the Admin API. Instead, each developer's Claude Code instance sends OpenTelemetry data straight to Axify using a token you generate in Axify.

Step 1 — Create the integration in Axify

  1. In Axify, go to Settings → Integrations.
  2. Click Add integration and choose Claude Subscription (under the AI tools category).
  3. Give it a name (e.g. Claude — Engineering) and click Create.

Axify generates an **ingestion token** (a signed JWT scoped to this integration and your organization). You can revoke and regenerate it at any time from the integration's settings.

Step 2 — Push the config to your team

Axify shows you the snippet to install:

{
 "env": {
   "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
   "OTEL_EXPORTER_OTLP_ENDPOINT": "https://ai-otel.axify.io",
   "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer <your-token>",
   "OTEL_EXPORTER_OTLP_PROTOCOL": "http/json",
   "OTEL_LOGS_EXPORTER": "otlp",
   "OTEL_METRICS_EXPORTER": "otlp"
 }
}

Pick one of the three install methods below. The Axify integration page walks through each one with the snippet pre-filled with your token — you can always come back to it.

Option A — Organization-wide via Claude Managed Settings (recommended)

Best if your team already uses claude.ai accounts. A Claude workspace Owner enables it once and every member's Claude Code starts reporting on their next session.

1. Open claude.ai → Admin settings → Managed Settings (Claude workspace admin access required).
2. Paste the snippet above into the env field.
3. Save. Every workspace member's Claude Code starts sending data on their next session.

The users of your organization will see this message. This is completely normal, Anthropic advocates for transparency and hints the user when a new setting is injected.

Option B — Organization-wide via MDM

Best if your company manages laptops via Jamf, Intune, Kandji, etc. Locks the config on every managed device, regardless of Claude account.

1. Open your MDM console and create or edit a configuration profile.
2. Add the snippet above under env in the Claude Code managed config.
3. Push the profile. Devices start sending data on their next Claude Code launch.

Option C — Just me (individual machine)

A good way to try Axify before rolling out to the whole organization.

1. Open `~/.claude/settings.json` on your machine (create it if it doesn't exist).
2. Paste the snippet above into the file.
3. Restart Claude Code — your sessions will start sending data to Axify.

What you'll see in Axify

  • Per-developer Claude Code usage (sessions, prompts, tokens, models used)
  • AI adoption metrics in the AI dashboard
  • Team and Contributor-level breakdowns

Frequently asked questions

Can I install both integrations?
Yes. If part of your org is on the Anthropic platform and part is on Claude.ai subscriptions, add both.

How do I revoke access?

  • Claude Platform: revoke the Admin API Key from the Anthropic console, or delete the integration in Axify.
  • Claude Subscription: regenerate the ingestion token from the integration page in Axify by clicking on renew. The old token stops working immediately; and once you set up the new token it will redistribute the new one to developers. 

Why don't I see usage right away?
We can't have historical data when you use Claude Subscription because we start collecting data once you add the integration. However, Axify sync its data every few hours so you will start seeing some data as you use it.

Is any code or prompt content sent to Axify?
No. Both integrations transmit only metadata — user identifier, timestamps, model, token counts, and similar usage attributes. Prompt and completion content stays with Anthropic.

If something doesn't work as expected, contact Axify support with the integration name and a screenshot of the error if available.
 

Related articles