---
title: "Connect Anthropic to Rig — Rig guide"
description: "Connect Anthropic to Rig with an Admin API key to sync Claude API usage and cost by day, model, workspace and key, plus Claude Code usage by person."
canonical: "https://rig.so/guides/connect-anthropic"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Anthropic to Rig

Sync your Claude API token usage and cost, Claude Code usage by person, and your organisation's users, workspaces and API key list into Rig. This connector reads the Anthropic Admin API for a Claude Console organisation and uses an Admin API key.

## Before you start

- You need an organisation on the Claude Console, with the **admin** role. Only admins can create an Admin API key, and individual accounts have no Admin API.
- This connector covers Claude API and Console usage. For Claude.ai seat usage on an Enterprise plan, use the Claude Enterprise connector instead.

## Step 1: Create an Admin API key

1. Sign in to the Claude Console as an organisation admin.
2. Open the Admin keys page at `platform.claude.com/settings/admin-keys`.
3. Create a new Admin API key. It starts with `sk-ant-admin`.
4. Copy the key and store it safely.

Use an organisation-wide key
A key scoped to a single workspace is refused when you connect. Create the Admin API key for the organisation.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **Anthropic**, open the card and click `Connect`.
3. **Admin API key**: the key from Step 1.
4. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

Anthropic lands in its own `anthropic` schema in your warehouse:

- **Usage and cost**: daily message token usage and cost reports, broken down by model, workspace and API key.
- **Claude Code usage**: daily Claude Code usage by person.
- **People and structure**: users, invites, workspaces and workspace members.
- **API keys**: key names and a redacted hint, never the key itself.

Cost amounts arrive in cents as text, so 123.45 means $1.23.

## Good to know

- The daily reports are re-read for the last few days every sync, so late adjustments land in the warehouse.
- Claude Code signed in with a claude.ai plan is not in the Admin API. Enterprise organisations get that data from the Claude Enterprise connector.
- The Admin API cannot create API keys. Rig only reads the list of existing ones.
- To disconnect Anthropic, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Track Claude API spend
- Understand token usage by model
- See who uses Claude Code

[More ideas for using Anthropic](https://rig.so/integrations/anthropic)

## Anthropic documentation

- [Admin API overview](https://platform.claude.com/docs/en/manage-claude/admin-api)
- [Which analytics API do you need](https://platform.claude.com/docs/en/manage-claude/analytics-api)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-anthropic)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)