Connecting to Anthropic

Connect your Anthropic account to CloudZero to bring your Anthropic cost and usage data into a unified view of all your cloud and AI spend. CloudZero organizes your Anthropic costs, along with your other costs, into categories (called Dimensions) that matter most to your business. For example: business unit, team, product, feature, environment, customer, or virtually anything else. Once connected and organized, you can quickly answer questions about your spend that matter to your stakeholders.

Anthropic sells two separate products that bill independently, and each one has its own CloudZero connection:

• Claude Console, the developer platform at platform.claude.com, where your applications call the Claude API and you pay for the tokens they consume. Use the Anthropic (Platform) connection, which breaks costs down by project, model, and operation. Available for any Claude Console organization.
• Claude.ai, the chat product at claude.ai, sold as seat-based or usage-based subscriptions. Use the Anthropic Enterprise connection, which breaks costs down by individual user, product, model, and context window. Requires a Claude Enterprise plan with analytics provisioned by Anthropic.

An organization can buy both products and configure both connections. Each connection is a distinct data source with no overlap: Anthropic (Platform) covers API usage (projects, models, operations), while Anthropic Enterprise covers Claude.ai product usage (such as Chat, Claude Code, and Cowork). To isolate one connection in Explorer, filter by the Dimension, Cloud Provider.

The Anthropic Enterprise connection supports these Claude.ai plans:

Usage-based and seat-based are the two Enterprise billing models Anthropic distinguishes in its Analytics APIs documentation. The Claude.ai pricing page does not use these terms, so if you are not sure which model your organization is on, check with your Anthropic account team.

Anthropic does not offer an API for Claude.ai Team seat data, so CloudZero cannot ingest it. A Team plan customer who also has a Claude Console organization can connect it with Anthropic (Platform), which captures API token spend. That spend is billed separately from Claude.ai Team seats and does not include them.

Anthropic (Platform)

The Platform connection ingests cost and usage data broken down by project, model, operation, and more. It connects through Anthropic's Usage and Cost API using an Admin API Key from the Claude Console at platform.claude.com. This connection is available to any Claude Console organization, whether prepaid or on a committed API contract. Anthropic's Admin API is not available to individual accounts, so if you have not set one up yet, create your organization in the Claude Console under Settings > Organization first.

What you need

• A CloudZero user with admin permissions
• An Anthropic Admin API Key. Only organization members with the Admin role can create Admin API Keys.

Step 1: Create an Admin API Key

1. Sign in to the Claude Console at platform.claude.com.
2. Go to Settings > Admin keys.
3. Select Create key, give it a descriptive name (for example, "CloudZero Integration"), and choose a key expiration.
4. Copy the key and store it securely. Anthropic does not display the key again after creation.

Step 2: Configure the connection in CloudZero

1. In CloudZero, go to Settings > Connections.
2. Select Create Connection +.
3. Select the Anthropic tile.
4. Enter a Connection Name. This label identifies the connection throughout CloudZero.
5. Enter the Admin API Key you created in Step 1.
6. Select Create Connection. You are redirected to the Connections page, where your new connection is listed.

What to expect

The connection status changes from Pending Data to Healthy once the first ingest completes. Your Anthropic costs appear across the platform within 24 hours.

Anthropic Enterprise

The Enterprise connection ingests per-user cost and usage data, broken down by user, product, model, and context window. It connects through Anthropic's Claude Enterprise Analytics API using an Analytics API Key created in Claude.ai. This connection requires a Claude Enterprise plan with analytics provisioned by Anthropic.

What you need

• A CloudZero user with admin permissions
• A Claude Enterprise plan with analytics provisioned by Anthropic
• The Primary Owner role on your Claude Enterprise organization. Only the Primary Owner can enable API access and create Analytics API Keys.
• An Analytics API Key with the read:analytics scope. This is a different credential from the Admin API Key used by the Anthropic (Platform) connection.

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.
2. Enable public API access if it is not already enabled.
3. In the Keys section, select Create key and give it a descriptive name (for example, "CloudZero Integration").
4. Select the read:analytics scope. Scopes are fixed when the key is created, so a key created without this scope cannot be used for this connection.
5. Copy the key and store it securely. Anthropic does not display it again.

For the full procedure and the complete scope list, see Anthropic's guide to creating a key for a Claude Enterprise organization.

Step 2: Create the connection in CloudZero

1. In CloudZero, go to Settings > Connections.
2. Select Create Connection +.
3. Select the Anthropic Enterprise tile.
4. Enter a Connection Name. This label identifies the connection throughout CloudZero.
5. Enter the Analytics API Key you created in Step 1.
6. Select Create Connection. You are redirected to the Connections page, where your new connection is listed.

What to expect

The connection status changes from Pending Data to Healthy once the first ingest completes. Your Anthropic Enterprise costs appear across the platform within 24 hours. CloudZero pulls up to 12 months of historical data on first connection. Data is not available prior to January 1, 2026.

Anthropic reconciles Enterprise billing data for up to 30 days, so recent month costs can shift slightly as Anthropic finalizes the numbers.

On seat-based Claude Enterprise plans, Anthropic's cost endpoints report usage credit consumption rather than the seat license fee, so the ingested totals cover usage credits only. Usage-based Enterprise plans report full cost.

Claude Code usage that runs through Amazon Bedrock is not included, because Anthropic's analytics API does not report it.

Tags

The Anthropic Enterprise connection provides tags with the anthropic_cz prefix for use in Dimensions:

Cloud Provider Dimensions

Once connected, you can group and filter your Anthropic Enterprise costs across the platform by the following categories (called Cloud Provider Dimensions):

Usage data

The connection calls four Anthropic API endpoints with your Analytics API Key:

• GET /v1/organizations/analytics/user_cost_report: per-user cost by product, model, context window, cost type, and token type, read in one-hour windows
• GET /v1/organizations/analytics/user_usage_report: per-user token usage by product, model, and context window
• GET /v1/organizations/analytics/skills: usage and spend for each skill, read twice a day
• GET /v1/organizations/me: your organization's ID and name, read once a month so the organization ID in CloudZero matches the one Anthropic shows you

No other part of CloudZero calls Anthropic with your key.

Cost by skill

The connection uses the skills report to divide each user's cost among the skills that user ran. The division reassigns cost CloudZero has already ingested, so your Anthropic Enterprise total stays the same. A skill's share is the cost of the requests that involved the skill. Those requests would have cost something without the skill too.

Each cost row attributed to a skill carries two line-item properties:

Neither property holds a user name or email address. Custom skills appear under the names your team gave them, so a skill named after a project or a client shows that name in CloudZero.

Line-item properties are separate from tags and do not appear as Dimensions on their own. To group or filter by skill, add a custom Dimension in CostFormation. The Properties source holds a cost row's line-item properties, and the Dimension extracts the skill from it with a Lookup transform:

Skill:
  Name: Skill
  Rules:
  - Type: GroupBy
    Source: Properties
    Transforms:
    - Type: Lookup
      Key: ai:skill

Use Key here, because Path treats the colon in ai:skill as a separator. Anthropic can add a display name to a skill after its cost is ingested, so one skill can appear under two ai:skill values. For a value that stays the same, use Key: ai:skill_id.

Costs with no skill attribution, such as Chat usage, have no value in this Dimension.

Skill properties are available for September 2026 onward. Earlier months carry them only if the connection is reingested.

For organizations that use customer-managed encryption keys, Anthropic does not count skills started with a slash command in Claude Code or Cowork, so cost by skill is understated. For details, see Anthropic's Claude Enterprise Analytics API documentation.