---
title: How to connect Anthropic Claude
canonical: "https://cloudmonitor.ai/docs/how-to/how-connect-anthropic-claude/"
description: "Generate an Anthropic Admin API key, then paste it into CloudMonitor to track token usage, prompt caching, batch discounts, and dollar cost per workspace."
---

This guide creates an Anthropic **Admin API key** so CloudMonitor can read Claude usage and cost data from your organization. Allow about 5 minutes. You need to be an Anthropic organization **owner** to complete it.

:::caution
**Admin keys are not regular API keys**

The Admin key used here is **distinct** from the API keys your applications use to call Claude. Pasting a regular API key fails the Verify step. Generate the Admin key from a separate page in the Anthropic Console — see Step 1.
:::

### Step 1 — Generate an Admin API key

Open [console.claude.com → Settings → Admin Keys](https://console.claude.com/settings/admin-keys).

Click **Create Admin Key**. Name it `CloudMonitor`. The key is shown only once — copy it now.

Admin keys are organization-scoped. They can read usage across every workspace you own and cannot call Claude models.

### Step 2 — Add the key in CloudMonitor

In the CloudMonitor Admin App, go to **Settings** → **AI providers** → **Anthropic Claude** → **Add connector**.

Paste the Admin key. Click **Verify**.

### Step 3 — Confirm the 14-day backfill

CloudMonitor pulls the most recent 14 days as proof the connector works. You should see:

- Token use broken down by workspace, API key, model, and service tier
- Prompt caching split into **uncached input**, **cache writes** (1.25× or 2× the standard input rate depending on TTL), and **cache reads** (0.1× the standard input rate)
- Standard, priority, and **batch** tier usage — batch is the 50% discount channel
- Dollar cost from the `/v1/organizations/cost_report` endpoint, in USD

If the totals match the **Usage** tab in the Anthropic Console, click **Save**.

### Step 4 — Polling cadence

CloudMonitor polls hourly for the current day and backfills T-2 daily. Reports refresh as new data lands.

:::tip
**What's exposed and what isn't**

- **Workspace** is the finest attribution grain. Anthropic does not currently expose per-user identifiers in the Admin API.
- **Managed Agents** runtime hours are billed separately from tokens. CloudMonitor reports both side by side once the Managed Agents endpoint is enabled in your organization.
- **Claude on AWS Bedrock or GCP Vertex AI** is not visible through Anthropic's Admin API — that usage flows through your AWS or GCP billing. Multi-cloud Claude attribution is on the roadmap.
:::

:::tip
**Troubleshooting**

- **"Unauthorized" on Verify** — you pasted a regular API key (the one used to call Claude). Re-create the Admin key from **console.claude.com → Settings → Admin Keys**.
- **Cache read tokens look unusually low in dollars** — they're reported separately on purpose. The Anthropic price for cache reads is 0.1× the standard input rate, so the dollar figure is correctly small relative to the token count.
:::

## What's next

- [How to read CloudMonitor's AI cost reports](/docs/how-to/how-interpret-ai-token-cost-reports/)
- [Does CloudMonitor see my AI prompts or responses?](/cloudmonitor-data-security-statement/)