Connect Anthropic
CloudQuell reads your Anthropic spend through a Claude Console admin key — dollars from Anthropic’s cost report (the billing source of truth) and token usage from the usage report. CloudQuell only ever calls the read-only usage and cost reporting endpoints — nothing is written back to your Anthropic organization. Once connected, Claude API spend flows into the same AI Spend view and ledger as your other providers.
Prerequisites
Section titled “Prerequisites”- An Anthropic Claude Console organization (the API platform at platform.claude.com). On an individual Console account, admin keys are unavailable — create an organization first under Settings → Organization. Claude Enterprise (claude.ai) organizations aren’t supported yet.
- An org admin role in that Anthropic organization — only admins can create admin keys.
- A CloudQuell admin — creating integrations requires the
super_adminoradminrole. See roles.
The three steps
Section titled “The three steps”1. Create an admin key
Section titled “1. Create an admin key”In the Claude Console, go to Settings → Admin keys (a separate page from API keys) and create a new admin key. Anthropic’s admin key guide walks through it.
Admin keys start with sk-ant-admin01-. Regular API keys (sk-ant-api…)
are scoped to running models and will not work — the usage and cost reporting
endpoints are organization-level and require an admin key.
2. Connect it in CloudQuell
Section titled “2. Connect it in CloudQuell”In the CloudQuell admin, go to Integrations, open the Anthropic tile, and click Connect. Paste the admin key. CloudQuell validates the key live against Anthropic before saving — a bad key (or a Claude Enterprise key) fails immediately, not on the first sync.
3. Done — the backfill starts
Section titled “3. Done — the backfill starts”That’s it. The key is stored in AWS Secrets Manager — never in the database — and the first ingest kicks off right away.
What data appears, and when
Section titled “What data appears, and when”On connect, CloudQuell backfills up to 12 months of history (shorter if your organization is younger), so you have trend context from the start. After that, Anthropic spend syncs daily — and each sync re-pulls a trailing 3-day window to absorb late corrections, so recent days may adjust slightly before settling.
Two sources feed the view:
- Dollars come from Anthropic’s cost report — the billing source of truth, so CloudQuell’s totals match your Anthropic invoice.
- Token usage comes from the usage report — the Messages API, including cache activity.
In the AI Spend view you can break Anthropic spend down by:
| Dimension | What you get |
|---|---|
| Model | Cost and tokens per Claude model. |
| Day | Daily trend. |
| Token type | Anthropic-native types: uncached input, cache writes, cache reads, and output tokens. |
| Workspace | Spend per Console workspace, with display names (archived workspaces included, so history stays attributed). |
| API key | Token and request attribution per key. Anthropic exposes no per-key dollars, so this dimension shows usage, not cost. |
| Service tier | Batch vs. standard — the Batch API runs at roughly a 50% discount, so this split shows your batch-adoption savings headroom. |
Rotate or replace the key
Section titled “Rotate or replace the key”You can rotate the key any time from the integration’s Manage dialog in Integrations — create a new admin key at Anthropic, paste it in, and it’s validated live and swapped in Secrets Manager. Rotation doesn’t interrupt or reset your ingested data. If the key is revoked at Anthropic, syncs stop until you paste a fresh one the same way.
Troubleshooting
Section titled “Troubleshooting”“Must start with sk-ant-admin01-”
Section titled ““Must start with sk-ant-admin01-””You pasted a regular API key (sk-ant-api…). Those run models but can’t read
organization-level cost data. Ask an org admin to create an admin key from
Settings → Admin keys.
“Claude Enterprise organizations aren’t supported”
Section titled ““Claude Enterprise organizations aren’t supported””The key belongs to a Claude Enterprise (claude.ai) organization, which doesn’t expose the usage and cost reporting endpoints CloudQuell reads. Only Claude Console (API platform) organizations can be connected today.
I can’t find “Admin keys” in the Console settings
Section titled “I can’t find “Admin keys” in the Console settings”Admin keys are an organization feature — individual Console accounts don’t have them. Create an organization first under Settings → Organization, then create the key under Settings → Admin keys as an org admin.
What’s not included
Section titled “What’s not included”- AWS Bedrock — Claude usage billed by AWS lands in your AWS cloud spend, so it’s excluded here to avoid double-counting. It’s covered by the AWS integration.
- Google Vertex AI — likewise billed by Google Cloud; covered by the Google Cloud integration.
- Claude.ai seat subscriptions (Pro, Max, Team, Enterprise) — seat licensing doesn’t appear in the API cost report, so it’s not in this integration.
Remove the integration
Section titled “Remove the integration”Deleting the Anthropic integration is a permanent hard delete: it removes all ingested Anthropic cost data and the stored key from Secrets Manager. This can’t be undone — see manage your integrations.
Query it from an agent
Section titled “Query it from an agent”The MCP server’s get_ai_spend tool defaults to
provider: "anthropic", so a connected agent can query Claude API spend by model,
token type, workspace, API key, or service tier in plain language.