> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudcapital.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Integrate Claude API
> Connect Anthropic Claude API (Console) org spend to Cloud Capital with a Console Admin API key. Claude API support is currently in Beta.
**Claude API support is in Beta.** To enroll, request access from your Cloud Capital Customer Success Manager. Once your account is enabled, **Claude API** appears as an option on the New Integration page. If you don't see it yet, reach out to your Customer Success Manager.
Using the **Claude.ai** app instead (people signing in at claude.ai for chat, Claude Code, or Cowork)? See [Integrate Claude.ai Enterprise](/get-started/claude-ai-data-integration). The two keys are not interchangeable.
Cloud Capital reads your **Claude API** usage from the Anthropic Console Admin API. You paste a **Console Admin API key** into Cloud Capital; the key is encrypted and stored on the integration. This path is **forecast-only** — Cloud Capital does not purchase commitments or bill Claude API spend on your behalf through this integration.
Setup takes about 5 minutes once you have an Admin API key.
***
### What Cloud Capital accesses
| What you're granting | How | Scope |
| --------------------- | --------------------------------------------------- | ---------------------------------------------------------------------- |
| Console Admin API key | Pasted into the integration form, encrypted at rest | Read access to Console Admin cost APIs for your Anthropic organization |
Cloud Capital uses the key only to **read** cost data. It does not create, modify, or delete resources in your Anthropic Console, and this integration does not enable commitment purchasing or billing transfer.
### What's available with Claude API today
| Available | Not yet available |
| -------------------------------------------------------------------------- | ------------------------------------------- |
| Cost forecasting, cost insights, and cost allocation for Console API spend | Commitment purchasing through Cloud Capital |
| Nightly ingest of daily cost data | Billing through Cloud Capital |
***
### Before you begin
* **Choose the right product** — Use Claude API if you get a developer bill at [console.anthropic.com](https://console.anthropic.com) for apps, agents, and API keys (`sk-ant-…`). If your team uses Claude.ai Enterprise seats, connect [Claude.ai](/get-started/claude-ai-data-integration) instead.
* **Admin access** — You need permission to create a **Console Admin API key** in your Anthropic Console organization settings. Admin keys start with `sk-ant-admin`.
* **Not covered here** — Max/Pro and Team (non-Enterprise) plans. Amazon Bedrock or AWS Marketplace Anthropic usage stays on your [AWS integration](/get-started/aws-data-integration) — connecting both paths for the same spend can double-count.
* **Wrong key types fail** — Inference keys and Claude.ai Analytics keys are rejected. Paste only a Console Admin API key.
### Setup
In Cloud Capital, go to the **Integrations** page — from Cost Allocation, use **Manage Cloud Providers**. Click **Create New Integration** and choose **Claude API**.
The new integration opens on the Integration Settings page. Give it a descriptive name — you can add multiple Claude API integrations, so the name is how you'll tell them apart.
In the [Anthropic Console](https://console.anthropic.com), open your **organization settings** and create a **Console Admin API key**.
The key must start with `sk-ant-admin`. Copy it once — Anthropic shows the full value only at creation time.
Do not use an ordinary inference key (`sk-ant-api03-…`) or a Claude.ai Analytics key (`sk-ant-api01-…`). Those call different APIs and will fail the connection test.
On the Integration Settings page:
1. Paste the Console Admin API key into the **Console Admin API key** field.
2. Click **Test Connection**. Cloud Capital verifies it can reach the Anthropic Console Admin API with this key.
3. After a successful test, set the integration status to **Enabled** (or leave it if the app already switched it for you).
4. Click **Save**.
You must complete a successful connection test before you can enable a new integration. To rotate a key later, paste a new key and re-test; leave the field blank to keep the stored key.
***
### What to expect after setup
* **Data timing** — Cost data is ingested on a scheduled nightly cycle, not instantly on save. Expect your first data in dashboards within about 24 hours of a successful connection.
* **Empty at first is normal** — If the Admin API has little or no recent usage, dashboards may look empty until spend appears and the next nightly cycle runs.
* **Forecast only** — Claude API spend appears in forecasting and cost insights. Commitment purchasing and billing transfer are not part of this integration.
### Troubleshooting
| Symptom | What to check |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Claude API card missing or Coming Soon | Your org is not enrolled yet. Ask your Customer Success Manager to enable `claudeApi`. |
| Connection test fails / 401 | Confirm you pasted a Console Admin key (`sk-ant-admin…`), not an inference or Analytics key. |
| Form blocks save with a key-type notice | You likely pasted a Claude.ai Analytics key or an inference key. Use a Console Admin key, or switch to [Claude.ai](/get-started/claude-ai-data-integration). |
| Spend also on AWS CUR for Bedrock / Marketplace | Keep Bedrock/Marketplace on AWS only. Connecting the same Anthropic spend on both Claude API and AWS can double-count. |
| Test passes but dashboards are empty | Allow up to 24 hours for nightly ingest. Confirm the Console shows recent API usage. |
***
For a full overview of how Cloud Capital handles data access, encryption, audit logging, and compliance, see the Security page.