> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/features/cost-loops/anthropic.md).

# Anthropic

Learn how to connect your Anthropic organization to North as a Cost Loop.

Connect the Anthropic Cost Loop with your North account to see your usage costs across the various models Anthropic provides.

## Before You Start

You need administrator access to your Anthropic organization, and your Anthropic organization ID. North verifies that the ID matches the organization tied to the key you supply, so the two must belong together.

North reads your Claude API usage and cost through the Anthropic Admin API. You supply your organization ID and an API key. Where you create that key depends on which Claude product you use. North asks you to pick one, and the setup steps change with your answer.

| Product type        | Where you administer it | Key you create    |
| ------------------- | ----------------------- | ----------------- |
| **Claude Platform** | platform.claude.com     | Admin API key     |
| **Enterprise**      | claude.ai               | Analytics API key |

Pick the one that matches how your organization buys Claude. If you are not sure, check which of the two sites you use to manage your organization.

## Connect Anthropic

{% stepper %}
{% step %}

### Open the connect screen

Open **Settings**, then **Integrations**, then **Add accounts**. Under **Cost Loops**, select **Anthropic**.
{% endstep %}

{% step %}

### Create your API key

**For Claude Platform:** in the Claude Console, open **Settings**, then **Admin keys**. Create an Admin API key with access to usage and cost reporting.

**For Enterprise:** in claude.ai, open **Organization settings**, then **API**. Create an Analytics API key with the `read:analytics` scope.
{% endstep %}

{% step %}

### Enter your connection details

Fill in the fields:

* **Connection name.** A label to recognize this account by. It becomes the card title on your homepage.
* **Anthropic organization ID.**
* **Claude product type.** Claude Platform or Enterprise.
* **Admin API key**, or **Analytics API key** for Enterprise. The field label changes with the product type you selected.
  {% endstep %}

{% step %}

### Verify and connect

Click **Verify & Connect**. North checks the key against the organization ID before it saves the connection.
{% endstep %}
{% endstepper %}

## What North Reads

North reads two reports from the Anthropic Admin API, plus a third for Claude Code.

| Report            | Frequency | Broken down by                                                      |
| ----------------- | --------- | ------------------------------------------------------------------- |
| Usage             | Hourly    | Model, workspace, service tier, context window, inference geography |
| Cost              | Daily     | Workspace and description                                           |
| Claude Code usage | Daily     | Not broken down further                                             |

{% hint style="info" %}
Usage carries more dimensions than cost. That is a property of the Anthropic Admin API, which caps a request at five grouping dimensions and reports cost at a coarser grain than usage.
{% endhint %}

## After You Connect

Anthropic spend appears on your homepage as a card carrying your connection name. See [Viewing Cost Loop Data](/docs/features/cost-loops/viewing-cost-loop-data.md) for where else it shows up and at what detail.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.north.cloud/docs/features/cost-loops/anthropic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.