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

# Claude.ai (Enterprise)

> Connect Claude Enterprise (claude.ai) Analytics API credentials to nOps Inform

## Overview

nOps uses an **Analytics API key** created in **claude.ai** to bring Claude Enterprise usage and adoption data into Inform, and—when the key has the right scopes—per-user spend and seat limits into **Budgets**. Credentials are stored securely, validated before save, and are not shown again after you connect.

<Note>
  This integration is for **Claude Enterprise** (claude.ai seats) only. If your organization uses **Claude Platform / Console** (programmatic API usage), see [Anthropic (Platform)](/integrations/anthropic) instead — the two credential types are **not** interchangeable. An Analytics key cannot call the Console Admin API, and a Console Admin key is rejected by the Enterprise endpoints.
</Note>

## Prerequisites

* Claude Enterprise organization with a member who can create an Analytics API key in claude.ai
* nOps organization **administrator** access

<Note>
  Only **admins** and **owners** can connect, re-validate, or disconnect. **Members** see **Admin Only** on connectable cards.
</Note>

## API key scopes

Create one Analytics API key in **claude.ai → Organization settings → API** and grant the scopes your team needs. nOps uses the [Claude Enterprise Admin API](https://docs.anthropic.com/en/api/admin) for seat tracking and limit changes in Budgets.

| Scope                    | Used for                                                        | Required?                                                          |
| ------------------------ | --------------------------------------------------------------- | ------------------------------------------------------------------ |
| **`read:analytics`**     | Inform — usage and adoption visibility                          | **Yes** (minimum to connect)                                       |
| **`read:members`**       | Budgets — match nOps users to Claude members by email           | Required for [AI seat tracking](/operate/budgets#ai-seat-tracking) |
| **`read:spend_limits`**  | Budgets — per-user spend and effective seat limits              | Required for AI seat tracking                                      |
| **`write:spend_limits`** | Budgets — set or clear per-user spend limit overrides from nOps | Optional (read-only limits if omitted)                             |

<Note>
  **Read-only seat tracking** — grant `read:analytics`, `read:members`, and `read:spend_limits`.\
  **Edit limits from Budgets** — also grant `write:spend_limits`. You can add scopes later and **Re-validate** in nOps without reconnecting from scratch.
</Note>

### Where each feature appears in nOps

| Feature                      | Location                                                                                    |
| ---------------------------- | ------------------------------------------------------------------------------------------- |
| Usage and adoption           | Inform cost and analytics workflows                                                         |
| Per-user AI spend and limits | **Operate → Budgets** → open a budget → **AI seat tracking** (opt in per budget)            |
| Inline limit edits           | Same table, **Seat limit** column (creators and admins only; requires `write:spend_limits`) |

## Create a Claude.ai Analytics API key

Claude **Enterprise** organizations do not appear in the Anthropic Console and have no Admin API keys. Their usage and adoption data comes from the **Claude Enterprise Analytics API**, which uses an **Analytics API key** created in claude.ai.

1. Sign in to [claude.ai](https://claude.ai).
2. Open **Organization settings → API**.
3. Enable public API access and **create an Analytics API key**.
4. Select scopes:
   * **`read:analytics`** — always required.
   * **`read:members`** and **`read:spend_limits`** — add these for [AI seat tracking in Budgets](/operate/budgets#ai-seat-tracking).
   * **`write:spend_limits`** — add this only if you want to adjust per-user limits from nOps.
5. Copy the key immediately and store it securely.

<Warning>
  Do not share the Analytics API key or expose it in public repositories. Generate a new key and reconnect if it is compromised.
</Warning>

## Connect in nOps

### Where to open Claude.ai (Enterprise)

* **To connect for the first time** — go to **Settings → Integrations** and click the **Claude.ai (Enterprise)** card.
* **To manage an existing connection** — go to **Settings → Account Status → Connected apps** and click the **Claude.ai (Enterprise)** chip to re-validate or disconnect.

### Connect steps

1. Click the **Claude.ai (Enterprise)** card or chip.
2. Enter an **API key name** and paste the **Analytics API key** (`sk-ant-api01-…`).
3. Click **Connect**.

nOps validates the key against the Claude Enterprise Analytics API before storing it.

## Manage your connection

Administrators can **Re-validate** or **Disconnect** from the connected modal. **Action required** means validation failed — confirm the key is still active in claude.ai and reconnect if needed.

## Troubleshooting

* **Invalid key** — confirm you used an **Analytics API key** created in claude.ai, not a Console Admin API key from [Anthropic (Platform)](/integrations/anthropic).
* **Missing scope / permission errors** — recreate the key in claude.ai with the scopes from [API key scopes](#api-key-scopes). For Budgets seat data, include **`read:members`** and **`read:spend_limits`**. For editing limits in Budgets, include **`write:spend_limits`**.
* **Seat tracking works but limit edits fail** — the key likely lacks **`write:spend_limits`**. Add that scope in claude.ai and **Re-validate** in nOps.
* **Rate limited** — Anthropic caps Admin API requests (for example, spend limit calls) at **60 requests per minute** organization-wide. Wait a moment and retry; nOps surfaces the rate-limit response in the budget UI.
* **No data** — allow up to **24 hours** after connect for usage data to populate in Inform. Budget seat rows appear after you enable tracking on a budget and save.
* **No account found in Budgets** — nOps matches users by **email**. Confirm the nOps user email matches the Claude member email.
* **Multiple organizations** — repeat connect with a unique **API key name** per Claude Enterprise organization.

## Security

Follow your organization's key rotation policy. Update nOps before rotating keys in claude.ai to avoid sync gaps.

## Related

* [Budgets — AI seat tracking](/operate/budgets#ai-seat-tracking) — enable per-budget seat spend and limits in Operate
* [Anthropic (Platform)](/integrations/anthropic) — separate integration for Claude Console / API usage (not claude.ai Enterprise seats)