Anthropic AI Consumption integration

Use the Anthropic AI Consumption integration to collect Claude Enterprise Analytics cost and usage data and load it into AI Usage Data in Yarken.

Supported Anthropic data source

This integration collects cost and usage data from Claude Enterprise Analytics for Claude Enterprise seats.

It uses a Claude Enterprise Analytics API key beginning with sk-ant-api01-. Anthropic Admin API keys beginning with sk-ant-admin01- are not supported by this integration.

What the integration provides

The integration helps you analyze Anthropic spend and token consumption by user, product, model, team, region, and supported cost meter.

• Per-user Anthropic cost data.

• Per-user token usage.

• Product, model, region, speed, and team attributes when Anthropic provides them.

• Separate AI Consumption records for supported token and tool meters.

• Optional reconciliation against organization-wide Anthropic cost.

• Normalized AI Consumption fields for reporting and chargeback.

Roles and responsibilities

Before you begin

Create the Anthropic Analytics API key

Complete these steps as the Claude Enterprise Primary Owner:

1. Sign in to Claude Enterprise.

2. Go to Organization settings > API.

3. Locate the Keys section.

4. Enable public API access if it is not already enabled.

5. Select + Create key.

6. Enter a descriptive name for the key.

7. Select read:analytics for Analytics data and read:members to resolve user IDs to email addresses.

8. If you use per-user spend governance, also select read:spend_limits.

9. Create the key.

10. Copy the secret and store it securely.

Authorize the Anthropic connection

1. Sign in to Yarken as an administrator.

2. Go to Admin > Pipelines > Connections.

3. Select the ADVANCED tab.

4. Open the Anthropic connection.

5. Complete the required connection fields.

6. Select Connect.

7. Confirm that the connection status changes to Connected.

For the general authorization workflow, see Authorize Advanced Connections.

How the integration works

The integration retrieves Anthropic Analytics data through the Yarken-managed Advanced Integration. You do not configure the underlying API calls or transformation logic.

1. Claude Enterprise provides user-attributed cost and usage data.

2. Anthropic Advanced Connection authorizes Yarken using the Analytics API key.

3. Yarken-managed integration workflow combines compatible cost and usage records and processes optional organization-level reconciliation.

4. Advanced pipeline runs the integration and records the execution result.

5. AI Usage Data stores the normalized usage and cost records for reporting and chargeback.

Data collection behavior

The integration collects data in daily UTC buckets. Yarken handles pagination and source grouping automatically.

A single user and day can produce several AI Consumption records because Anthropic reports different cost meters separately, including input tokens, output tokens, cache usage, web search, and code execution.

How data appears in AI Consumption

Cost reconciliation and unallocated spend

User-level Anthropic Analytics data contains activity that Anthropic can attribute to named Claude Enterprise seats. Direct API-key or automation traffic can be absent from those user-level results.

When organization reconciliation is enabled, Yarken compares de-duplicated user-attributed cost with the organization-wide Anthropic cost.

• If the totals match, Yarken does not add a reconciliation record.

• If the organization-wide total is higher, Yarken can create an additional unallocated AI Consumption record for the difference.

• Unallocated spend can represent Anthropic activity that is not tied to a named Claude Enterprise seat, such as direct API-key or automation traffic.

Important data interpretation guidance

Team overlap

Anthropic can repeat a user's full spend for each team the user belonged to during the UTC day. Do not add team-level billed cost directly when reconciling to the invoice total. Yarken removes team overlap during invoice reconciliation.

Meter-split records

A user, day, and model combination can create separate records for input, output, cache, web search, code execution, and other meters. A single meter record does not represent the user's total daily spend.

Seat cost and organization total

User-attributed cost can be complete for seat-level chargeback while excluding API-key or automation spend. Review unallocated cost when reconciling against the organization total.

Reporting lag

Anthropic Analytics exports refresh approximately every four hours and can continue to change for about 30 days. Treat recent data as provisional when reconciling it against other systems.

Run and monitor the Advanced pipeline

After the Anthropic connection shows Connected:

1. Go to Admin > Pipelines > Pipelines.

2. Select the ADVANCED tab.

3. Locate the Anthropic pipeline.

4. Select Run when you need an immediate execution, or keep recurring execution active as configured for your environment.

5. Open the pipeline to review the latest status and run history.

See Manage Advanced pipelines for the common pipeline controls.

Validate the integration

After the first successful run:

• Confirm the Anthropic connection shows Connected.

• Confirm the Analytics API key begins with sk-ant-api01-.

• Confirm public API access remains enabled.

• Confirm the key includes read:analytics and read:members.

• Confirm Anthropic appears as the provider in AI Consumption.

• Confirm expected users and models are present.

• Confirm token meters and costs are populated for the expected periods.

• If reconciliation is enabled, review any unallocated record and confirm the difference is expected.

Troubleshooting

Security and credential management

• Store the Analytics API key in an approved secrets manager.

• Do not expose the full key in screenshots, documentation, email, chat, or support tickets.

• Rotate or revoke the key according to your organization's security policy.

• If you replace the key, update the Anthropic Advanced Connection and confirm it returns to Connected.

• Run the Anthropic pipeline after credential rotation to validate the integration.

Related content

• Advanced integrations

• Authorize Advanced Connections

• Manage Advanced pipelines

• Troubleshoot Advanced Integrations