Connect to Anthropic

Workforce Intelligence connects to Anthropic through two separate connectors, Claude Console and Claude Enterprise. Both feed AI Cost Tracking.

Which Connection do I need?

Choose the connection that matches where your organization uses Claude. Organizations that use both need one key for each.

Use both connections if your teams use the Claude API through the Claude Console and also have Claude Enterprise seats. The two connectors report separate spend, and each one needs its own key. The two key types are not interchangeable.

Connect Using the Claude Console

The Claude Console connection pulls daily Claude API usage and spend for a single Claude Console organization through Anthropic's Usage and Cost API. For Claude Code activity, it also calls Anthropic's Claude Code Analytics API.

What is and isn't included

• Included: all Claude API usage in that Claude Console organization, not only Claude Code.

• Not included: claude.ai seats. Use the Claude Enterprise connection for those.

• Not included: Priority Tier costs. The cost endpoint does not report them, so spend for Priority Tier usage can be understated.

• Not available: Claude Platform on AWS. The Usage and Cost API endpoints are not available there, so that usage cannot be imported.

How it's used

This is one of the sources for AI Cost Tracking, alongside Claude Enterprise and, where enabled, OpenAI Platform. The Usage and Cost API reports spend by API key, workspace, model, and similar dimensions. It does not report spend by person, so Workforce Intelligence works out who the spend belongs to, and then which Jira work items it supports, in three steps:

1. Spread cost across usage. Each day's billed cost is divided across the usage recorded for each API key or Claude account, model, and context window.

2. Match usage to a person. Usage from a Claude account goes to the person who owns that account. Usage from an API key goes to the person who created that key. The person is matched to a Workforce Intelligence contributor by email address. Keys that several people share are credited to the person who created the key.

3. Match the person to work items. Workforce Intelligence looks at that person's GitHub activity (commits, pull requests, reviews, and comments) on the same day, in UTC. GitHub activity is linked to a Jira work item when a Jira work item key (for example, ABC-123) appears in the commit message or branch name, or in the pull request title or branch name. Where activity is linked to Jira work items, the person's spend for the day is split across those work items, in proportion to lines of code changed or, when line counts are not available, evenly by number of GitHub events.

Spend is attributed to Jira work items based on work activity detected on the same day. Spend that can't be matched to a person, or to GitHub activity linked to a work item on that day, still counts toward the total for this connection and is labeled Unattributed.

Step 1: Create an Admin API Key

1. Sign in to the Claude Console at https://platform.claude.com.

2. Go to Settings > Admin keys.

3. Select Create key, give it a name, choose a key expiration, and then select Create.

4. Copy the key and store it securely. Anthropic does not display the key again after creation.

Only members with the admin role can create the key. The Admin API isn't available to individual accounts. See Admin API and Create an Admin API key.

Step 2: Configure the connection in Workforce Intelligence

1. In Workforce Intelligence, go to Settings > Connectors.

2. Look for the Claude Code (Claude Console) connector and select Connect.

3. Enter your organization’s Console Admin API Key and select Verify & connect.

Once verified, Workforce Intelligence automatically pulls the last 90 days of Claude Console data, and then keeps it up to date daily. The most recent 3 days are refreshed on each daily sync.

Connect Using Claude Enterprise

The Claude Enterprise connection ingests cost and usage data by user and product, using an Analytics API key, through Anthropic's Analytics APIs. Unlike the Claude Console connection, this data includes the user, so spend is matched to a person by the email address on their Claude Enterprise account.

Before you connect

• Plan type. The cost and usage endpoints apply to usage-based Claude Enterprise plans. On seat-based plans, they reflect usage credits only, so AI Cost Tracking will not show your full seat spend. Check your plan type before you rely on this connection for cost reporting.

• Amazon Bedrock. Claude Code usage through Amazon Bedrock isn't returned by the Claude Enterprise Analytics API, so it does not appear in this connection.

How it's used

Like the Claude Console connection, this feeds AI Cost Tracking. Spend is matched to a person by email, and is then split across the Jira work items linked to that person's GitHub activity on the same day (UTC), in the same way as described for the Claude Console connection. Spend that can't be matched to a person or to a work item still counts toward the total for this connection and is labeled Unattributed.

Step 1: Create an Analytics API Key

1. As the Primary Owner of your Claude Enterprise organization, sign in to claude.ai and go to Organization settings > API. Other organization owners can't create this key. They can only create keys with Compliance API scopes.

2. Enable public API access.

3. Create a new Analytics API key. Note: the key needs the read:analytics scope. Scopes are fixed at creation, so a key without that scope will need to be recreated.

4. Provide a name (for example, “Workforce Intelligence Integration”).

5. Copy the key and store it securely. Anthropic does not display the key again after creation.

Step 2: Configure the connection in Workforce Intelligence

1. In Workforce Intelligence, go to Settings > Connectors.

2. Look for the Claude (Enterprise) connector and select Connect.

3. Enter your organization's Analytics API Key and select Verify & connect.

Once verified, Workforce Intelligence automatically pulls the last 90 days of Claude Enterprise data, and then keeps it up to date daily. Each daily sync re-pulls the last 30 days, because Anthropic can revise these values after the fact.

Manage Your Key

Replace a Key

To switch to a new key (for example, before the current key expires), disconnect the connector and connect it again with the new key. The steps are the same for both connectors.

1. Create a new key in Anthropic, following Step 1 for the connector (Admin API key for the Claude Console, Analytics API key for Claude Enterprise).

2. In Workforce Intelligence, go to Settings > Connectors and find the connector.

3. Select Disconnect, and confirm.

4. Select Connect, enter the new key, and select Verify & connect.

5. After the new connection is verified, revoke the old key in Anthropic.

Data that Workforce Intelligence has already imported is kept. Connecting again starts a fresh 90-day import, which updates existing records rather than duplicating them, so reporting for that period can take several hours to settle.

If a key expires or is revoked before you replace it, the connector shows Attention with a message that the key is no longer valid, and imports pause. Select Reconnect and enter a new key to resume. If the key is missing a required permission, the connector shows a message asking you to reconnect with a key that has full access.

Disconnect the Connector

1. In Workforce Intelligence, go to Settings > Connectors and find the connector.

2. Select Disconnect, and confirm.

Workforce Intelligence stops accessing Anthropic. Data that was already imported is kept, and continues to appear in AI Cost Tracking, but no new data is imported. To reconnect later, select Connect and enter a key.