> 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 usage and cost through an Anthropic API. You supply your organization ID and an API key. Which API North uses, and where you create that key, depend 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 | API North reads | | ------------------- | ----------------------- | ----------------- | ------------------------ | | **Claude Platform** | platform.claude.com | Admin API key | Admin API | | **Enterprise** | claude.ai | Analytics API key | Enterprise Analytics API | Pick the Claude product type that matches how your organization buys Claude. If you are not sure, check which of the two sites you use to manage your organization. If you pick Enterprise, you must be the Primary Owner of your Anthropic organization to create the Analytics API key. ## 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**. Open the [Claude Console Admin keys](https://platform.claude.com/settings/admin-keys) page to go there directly. Create an Admin API key with access to usage and cost reporting. **For Enterprise:** in claude.ai, open **Organization settings**, then **API**. Open the [claude.ai API settings](https://claude.ai/admin-settings/api-access) page to go there directly. Create an Analytics API key with the `read:analytics` scope. {% endstep %} {% step %} ### Enter Your Connection Details Fill in the Anthropic fields: * **Connection name.** A label to recognize this account by. It becomes the card title on your homepage. * **Anthropic Organization ID.** On Enterprise, claude.ai can show both an Organization ID and a Parent Organization ID. Enter the 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 API key against the Anthropic organization ID before it saves the connection. {% endstep %} {% endstepper %} ## What North Reads The reports North reads depend on the Claude product type you selected. ### Claude Platform On Claude Platform, 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 %} ### Enterprise On Enterprise, North reads two reports from the Anthropic Enterprise Analytics API. | Report | Frequency | Broken down by | | ------ | --------- | --------------------------------------------------------------------------------------------- | | Usage | Hourly | Model, product, context window, inference geography, speed, RBAC group | | Cost | Daily | Model, product, cost type, token type, context window, inference geography, speed, RBAC group | ## 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.north.cloud/docs/features/cost-loops/anthropic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.