Anthropic Integration
Last updated: October 1, 2026
Connect Anthropic as a Billing Source in Kion
This guide walks you through connecting your Anthropic account to Kion so you can view, track, and govern your Anthropic spend alongside the rest of your cloud and AI portfolio.
Before You Start
Kion pulls cost and usage data from two Anthropic APIs depending on your plan. The Admin API is available to Team and Enterprise organizations through the Anthropic Console and provides workspace- and API-key-level visibility. Enterprise customers can optionally also connect the Enterprise Analytics API, accessed through claude.ai, to add per-user breakdowns by product and model.
What this integration supports:
Anthropic Team plan organizations using the Claude API
Anthropic Enterprise plan organizations using the Claude API. This gives you workspace- and API-key-level cost and usage visibility
Anthropic Enterprise plan organizations with analytics enabled. Connecting the Analytics API adds per-user breakdowns by product and model (such as Chat, Claude Code, and other Enterprise products)
What this integration does not support:
Seat-based and subscription billing. This integration covers API usage billed through the Anthropic Console only. Seat-based charges for Claude.ai Team, Enterprise seats, Claude Code subscription-based access, and individual consumer plans (Free, Pro, Max) are not exposed through a cost or usage API and will not appear here. Anthropic usage routed through AWS Bedrock, Google Cloud Vertex AI, or Azure Marketplace. Those costs appear in your existing AWS, GCP, or Azure billing connections in Kion and are already ingested for visibility.
If you are unsure how your organization purchases Anthropic, check console.anthropic.com. If your team logs in there and has API keys, this guide applies to you.
What You Will Need
Before starting the setup in Kion, confirm you have the following:
Requirement | Details |
|---|---|
Anthropic organization | Your team must be set up as an organization in the Anthropic Console, not just individual accounts. Individual accounts do not have access to Admin API keys. |
Anthropic Team or Enterprise plan | Admin API keys or Analytics API keys are only available on Team or Enterprise plans. Individual accounts (Free, Pro, Max) are not supported. |
Organization Admin role in Anthropic | For Platform API spend, only users with the Admin role in the Anthropic Console can create Admin API keys. Standard developer accounts cannot. |
Anthropic Admin API key | A dedicated key created for this integration (see steps below). Admin keys begin with |
Anthropic Organization ID | A UUID that identifies your Anthropic organization. You can find it in the Anthropic Console under Settings > Organization, or in any API response header as |
Anthropic Analytics API key | A key with the |
Kion permissions | You must have a Kion role with permission to add billing sources or cloud integrations. Contact your Kion administrator if you are unsure. |
Step 1: Set Up Your Anthropic Organization (If Needed)
Admin API keys are not available for individual Anthropic accounts. If your team has been using Anthropic through individual accounts and has not yet set up an organization, do this first.
Sign in to the Anthropic Console at console.anthropic.com.
Navigate to Settings > Organization.
Follow the prompts to create or configure your organization and invite team members.
Once your organization is configured, continue to Step 2.
Step 2: Create a Dedicated Admin API Key in Anthropic
Kion uses an Admin API key to read cost and usage data from Anthropic's API. Create a dedicated key for this integration rather than reusing an existing key. This makes it easier to revoke access without disrupting other integrations if you ever need to rotate credentials. This step is optional. You can connect Kion with just the Analytics API key in the step below.
Sign in to the Anthropic Console at console.anthropic.com.
In the left navigation, click Admin keys. (Alternatively, click your username or organization name in the lower-left corner, select Organization settings, then click Admin keys in the left navigation.)
Click Create Admin Key.
Give the key a descriptive name, such as
Kion Integration.Copy the key immediately. Anthropic only displays this value once. If you close the dialog without copying it, you will need to revoke and regenerate.
Admin keys begin with sk-ant-admin. Store this key in a secure location before continuing.
A note on permissions: Anthropic Admin API keys currently only come in one permission level. They have read-write access to your organization's admin endpoints. Anthropic does not yet offer fine-grained scoping. Kion only reads from the Usage and Cost API and does not perform any write operations or cost-incurring actions. No prompt content or user data is ingested, only usage metadata such as token counts, model names, and workspace identifiers.
Step 3: Generate an Analytics API Key (Enterprise Customers Only)
If your organization is on the Anthropic Enterprise plan with analytics enabled, you can generate an Analytics API key to unlock per-user cost and usage visibility in Kion. This step is optional. You can connect Kion with just the Admin API key and add the Analytics API key later.
Important: The Analytics API key is separate from the Admin API key and is generated through claude.ai, not the Anthropic Console. Only a Primary Owner of the Claude Enterprise organization can create this key.
Sign in to claude.ai as a Primary Owner of your Claude Enterprise organization.
Navigate to your organization's settings and locate the Analytics API section.
Generate a new Analytics API key. Ensure the key includes the
read:analyticsscope.Copy the key immediately and store it securely — you will not be able to view it again.
Store this key alongside your Admin API key. You will enter it in the Kion billing source setup in the next step.
Step 4: Add Anthropic as a Billing Source in Kion
With your Admin API key ready, you can complete the setup in Kion in a few minutes.
Log in to your Kion instance.
Navigate to Accounts in the left navigation.
Select Billing Sources.
Click Add Billing Source and select Anthropic from the list of available providers.
Enter a Billing Source Name (for example,
Claude Billing Source).Paste your Admin API key (
sk-ant-admin...) into the Admin API Key field (if applicable)Paste your Analytics API key into the Analytics API Key field. If you do not have one or choose to skip this, leave the field blank — workspace- and API-key-level data will still be imported. (if applicable)
Set a Billing Start Date — this is the earliest date Kion will import cost data from. Anthropic's API supports historical data, so set this to the date your organization started using the Claude API, or the earliest date you want visibility into.
Click Add Billing Source.
Kion will validate the credentials and begin importing cost data. The initial import backfills historical data starting from your configured Billing Start Date.
What Data Kion Pulls In
Once the connection is active, Kion ingests cost and usage data from the Anthropic Usage and Cost API and the Analytics API. Data is broken down along the following dimensions:
Dimension | Description |
|---|---|
Organization | Your top-level Anthropic billing account |
Workspace | Anthropic workspaces within your organization, which map to Kion Accounts |
API Key | The specific API key that generated the usage, useful for attributing costs to individuals. This will show up as resource ID on service details or within Resource Identifier for Scopes. Because the Anthropic Usage API does not supply cost data at the key level, Kion maps cost to individual keys using proportional tokens and model usage. Small discrepancies are possible if an API key is using certain features, such as "Fast Mode". |
Model | The Claude model used (e.g., claude-sonnet-4-6, claude-opus-4-6). This will show as Services in spend reports. |
Operation / Charge Type | The type of token usage, including: uncached input tokens, cache write tokens, cache read tokens, and output tokens. This will show up as Usage Type in resource details and under SKU meter in spend reports. |
User | The individual Anthropic user whose activity generated the usage |
Product | The Anthropic product used (e.g., Chat, Claude Code, API) |
Operational Metrics | Commits, pull requests, cache optimization, etc.. are also made available via the Analytics API. Kion will continue to surface new metrics and data overtime for users of this API. |
This level of detail lets you build Kion spend reports, budgets, enforcements, and proper cost allocation around your Anthropic usage the same way you would for AWS, Azure, GCP, and OCI.
Important Limitations to Know
Per-user analytics require the Enterprise plan and Analytics API. Per-user breakdowns by product and model are only available to Anthropic Enterprise customers with analytics enabled, and only when the Analytics API key is connected. Workspace- and API-key-level visibility is available to all Team and Enterprise customers via the Admin API alone.
Seat-based and subscription charges are not supported. This integration only covers API usage billed through the Anthropic Console. It does not capture seat-based or subscription costs regardless of plan. If your organization pays for Claude.ai Team seats, Enterprise seats, Claude Code subscription-based access, or individual consumer plans (Free, Pro, or Max), those charges are billed separately and will not appear through this connection. Only token-based API usage metered through the Anthropic Console is visible here.
Bedrock, Vertex AI, and Azure Marketplace usage is not included. If developers on your team call Claude through cloud provider marketplaces, that spend flows through your AWS, GCP, or Azure billing data, not this connection. That spend will show up in spend reports under cloud provider services.
Claude Platform on AWS is not supported. If your organization accesses Claude through Anthropic's AWS-hosted platform (distinct from AWS Bedrock), the programmatic Usage and Cost API endpoints are not currently available for that deployment. You can view usage and cost data directly in the Anthropic Console instead. This is a constraint of the Anthropic API, not Kion.
Admin keys have broad permissions. Until Anthropic introduces fine-grained Admin API key scopes, any Admin key you create has read-write access to your organization's admin endpoints. Kion only reads from the Cost API, but treat this key with the same care as any privileged credential. Rotate it according to your organization's key management policy and revoke it immediately if it is ever exposed.
There is a minimum token threshold for cost data. Very low-volume API usage may result in delayed or sparse cost data. This is a constraint of the Anthropic API, not Kion.
Troubleshooting
Connection fails with an authentication error. Double-check that you are using an Admin API key (sk-ant-admin...) and not a standard API key (sk-ant-api...). Standard API keys do not have access to the Usage and Cost API. Regenerate an Admin key from the Anthropic Console if needed.
No data appears after connecting. Anthropic's cost data typically has a processing lag of a few hours. If the connection shows as active but no data appears after 24 hours, confirm that your organization has had API usage during the period you are viewing.
Per-user data is not appearing after connecting the Analytics API. Work through the following checks in order: confirm your Anthropic organization is on the Enterprise plan with analytics enabled; verify the Analytics API key was created by a Primary Owner in claude.ai; confirm the key includes the read:analytics scope; and allow for Anthropic's documented three-day processing delay on Analytics API data before assuming the connection is broken.
The Admin keys menu is not visible in the Anthropic Console. Admin keys are only available to users with the Admin role in an Anthropic organization on the Team or Enterprise plan. Individual accounts and accounts with Developer or Billing roles cannot create Admin keys. Ask your Anthropic organization admin to either create the key on your behalf or elevate your role.