> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/ai/claude.md).
# Claude
Claude is Anthropic's AI assistant, used by organizations for coding, writing, analysis, and automation. Claude Code is Anthropic's agentic coding tool for software engineers. Connecting Claude to Harmony via the Anthropic Admin API gives IT teams visibility into AI tool adoption and spend - tracking who is using Claude and Claude Code, how much token capacity they're consuming, and when they were last active.
#### What the Claude integration enables
| Capability | Description |
| ---------------------- | ------------------------------------------------------------------------------------------------ |
| User Discovery | Surface all Claude users in Harmony's software inventory, including org admins and invited users |
| Token Usage Tracking | Monitor per-user token consumption across Claude and Claude Code |
| Cost Visibility | See estimated USD spend broken down by user and by individual API key |
| Activity Monitoring | Track login and usage activity to identify inactive seats |
| Multi-Instance Support | Connect multiple Anthropic organizations if needed |
#### Prerequisites
* **Anthropic Organization Admin**: Must be an admin of the Anthropic organization
* **Admin API Key**: A key starting with `sk-ant-admin-` (see below)
* **Harmony Account**: Active Harmony workspace
{% hint style="warning" %}
Only **Admin API keys** (starting with `sk-ant-admin-`) are supported. Regular API keys (`sk-ant-api03-...`) will not work. Harmony validates the key format as soon as you paste it and will alert you immediately if the wrong key type is used.
{% endhint %}
#### Connect Claude to Harmony
**Step 1: Generate an Admin API Key**
1. Go to [Claude Console](https://console.anthropic.com) and sign in as an organization admin
2. Navigate to **Settings** > **Organization** > **API Keys**
3. Click **Create Key**
4. Select **Admin** as the key type, enter a name (e.g. `Harmony Integration`), and click **Create**
5. Copy the key - it starts with `sk-ant-admin-` and will not be shown again
**Step 2: Navigate to Integrations**
1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **Claude** under **SaaS Applications** and click **Connect**
**Step 3: Enter Credentials**
1. Paste your **Admin API Key**
2. Click **Connect**
Harmony validates the key format inline as soon as you paste it. If you have used a standard API key instead of an admin key, you will see an immediate warning before saving - preventing silent misconfigurations that could cause the integration to fail after setup.
{% hint style="info" %}
For organizations with multiple Anthropic accounts, you can add multiple instances by repeating this process for each account.
{% endhint %}
#### How Claude instances appear in Harmony
If you have both a Console connection and a Claude Enterprise Analytics connection, Harmony distinguishes between them clearly in your inventory:
* Your Console connection is labeled **Claude**
* Your Claude Enterprise Analytics connection is labeled **Claude.ai Enterprise**
Both instances are grouped together under a single Claude application card. No configuration changes are needed - existing connections update automatically.
#### What Harmony Syncs
**From Anthropic:**
* Users (name, email, role, account status) - including both org-level admins and accepted invited users
* Per-user token consumption (Claude and Claude Code)
* Per-API-key usage and estimated USD cost
* Login and activity data
* Workspace and organization membership
**User visibility**
Harmony pulls in your complete Anthropic user base from two sources:
* **Org admins** - sourced from Anthropic's users endpoint
* **Accepted invited users** - sourced from Anthropic's invites endpoint
Pending invites and users without an email address are automatically excluded. This means your full Claude user base is reflected accurately in Harmony, not just a limited subset of top-level administrators.
**API key usage and cost breakdown**
Claude API usage and estimated USD cost are tracked per individual API key, giving you granular visibility into how each key consumes your Anthropic budget. Each key is reported with its name and owner (email and display name). Costs are derived from Anthropic's rate table across model, service tier, context window, inference geography, and token type, reconciling to your organization's total spend.
Previously, cost data was only available at the organization level - now you can see exactly which keys are driving usage.
**Estimated cost on instance users table**
The **Estimated Cost** column on the instance users table shows each user's total estimated USD spend, sortable ascending or descending. Hovering over a cost cell shows a tooltip that breaks down spend by Claude model (for example, claude-3-5-sonnet, claude-3-opus), rounded to two decimal places.
#### Use Cases
AI Spend Management
Track token usage and estimated USD cost per user, per API key, and per team to allocate Claude costs accurately and forecast spend
Claude Code Adoption
Measure Claude Code usage across engineering teams to understand developer AI tool adoption
License Reclamation
Identify inactive Claude users and reclaim seats to optimize subscription costs
Offboarding
Confirm Claude access has been revoked when employees leave, as part of Harmony offboarding workflows
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.harmony.io/integrations/ai/claude.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.