> ## Documentation Index
> Fetch the complete documentation index at: https://docs.juneops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Enterprise Integration

> Connect Claude Enterprise (claude.ai) with June to track billed, per-person Claude spend across all products

This is the recommended way to connect Claude. If you're on the Anthropic Console / API instead, see [Claude Platform](/integrations/claude-platform).

## What you'll accomplish

* Connect with your claude.ai **Analytics API key** and **Compliance API key**
* Track **billed** Claude spend over time, by model, by department, and per person
* See every Claude seat, including people who have access but no usage (the seats you may be paying for and not using)
* Identify top users and the teams driving usage
* Get per-person totals that reconcile to your Anthropic bill
* Optionally, add an **Admin API key** to see each person's configured Claude spend limit next to their actual spend

## What June syncs

From your Claude Enterprise account, June syncs:

* **Billed spend per person**, across **all** Claude products (chat, Code, and more)
* **Token usage per person**
* **Your member roster**, so June can show every seat, including people with no usage
* **Per-person spend limits** (optional, with an Admin API key), so you can compare each person's cap against what they actually spend

Because every figure is billed and attributed to a person, your per-person and per-department totals reconcile to your Anthropic invoice. Usage history is available from January 2026 onward and refreshes daily.

<Note>
  Claude Enterprise uses **two required keys**: the **Analytics** key reads your spend and usage, and the **Compliance** key reads your member roster so June can show every seat (including unused ones). A third key, the **Admin API key**, is optional: it lets June read the spend limits you've configured in Anthropic, so each person's cap shows next to their actual spend. Without it, everything else works; you just won't see limits.
</Note>

## Capabilities

This is a read-only spend integration. June ingests usage and billing data, and does not take actions in Anthropic.

| Capability                                | Description                                                                                                                                                                |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Billed spend**                          | Your authoritative Anthropic invoice total over the selected period, net of account credits.                                                                               |
| **Spend over time**                       | Cumulative spend/tokens by model or department across the period.                                                                                                          |
| **Per-person spend (billed)**             | Billed spend and tokens attributed to each employee, across all Claude products. Searchable, sortable, and groupable by department.                                        |
| **Seat coverage**                         | Every Claude seat in one view, including unused (idle) seats. Surfaces who has access but no usage, and people who left but still hold a seat.                             |
| **Per-department & per-model breakdowns** | Where spend concentrates, plus top users.                                                                                                                                  |
| **Credits reconciliation**                | Used spend minus account credits equals your billed total, surfaced explicitly.                                                                                            |
| **Spend limits** (optional)               | Each person's configured Claude spend limit shown beside their actual spend, so you can spot who is close to their cap and who has no cap set. Requires the Admin API key. |

## Prerequisites

Before starting, ensure you have:

* A Claude **Enterprise** (claude.ai) plan, with the **Compliance API** enabled for your organization
* **Primary Owner** access to generate API keys

## Connect Claude Enterprise

<Steps>
  <Step title="Generate an Analytics API key">
    1. Sign in to [claude.ai](https://claude.ai) as a **Primary Owner**.
    2. Go to **Analytics → API keys**.
    3. Create a new key and copy it. This is your **Analytics API key** (it carries the `read:analytics` scope by default).
  </Step>

  <Step title="Generate a Compliance API key">
    This key lets June read your member roster, so it can show every seat (including unused ones).

    1. Go to **Organization settings → API** and create a key.
    2. Select the **`read:compliance_user_data`** and **`read:compliance_org_data`** scopes, and copy it. This is your **Compliance API key**.
    3. If those scopes aren't available, your organization needs the **Compliance API** enabled first. Request it from Anthropic, then create the key.
  </Step>

  <Step title="(Optional) Generate an Admin API key">
    This key lets June read the per-person spend limits you've configured in Anthropic, so caps show beside actual spend in June. Skip it if you don't use spend limits.

    1. Sign in to the [Anthropic Console](https://console.anthropic.com) as an admin.
    2. Go to **Settings → Admin keys** and create a key (it starts with `sk-ant-admin`).
    3. Copy it. This is your **Admin API key**.
  </Step>

  <Step title="Add the integration in June">
    1. In June, open the **Integrations** page.
    2. Choose **Claude Enterprise**.
    3. Paste your **Analytics API key** and your **Compliance API key** (and the **Admin API key**, if you created one), then save.
  </Step>

  <Step title="Wait for the first sync">
    June backfills your historical usage and refreshes daily. Spend, per-person data, and seats appear under **AI usage → Claude** once the first sync completes.
  </Step>
</Steps>