> For the complete documentation index, see [llms.txt](https://docs.trycaliber.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trycaliber.ai/connect-your-providers/anthropic-claude.md).

# Anthropic (Claude)

Connect Claude from Anthropic. Enterprise uses Anthropic APIs; Team needs the Caliber station plugin.

Caliber treats **Anthropic** as the provider. Claude (including Claude Code) is Anthropic’s product. In Settings the integration card is still labeled **Claude Code**.

How you bring analytics into Caliber depends on your Anthropic license:

| License               | How Caliber gets analytics                                                                                                                                                 |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Claude Enterprise** | Admin connects Anthropic **Admin API** and/or **Enterprise Analytics** keys. Caliber syncs usage, cost, and analytics from Anthropic’s APIs.                               |
| **Claude Team**       | Anthropic does not expose an org analytics API for Team. Deploy the **Caliber station plugin** so Caliber can collect the usage analytics you need from enrolled machines. |

{% tabs %}
{% tab title="Enterprise: Admin API key" %}
**Who:** Anthropic Console **Org Owner** (Admin Keys).

1. In Caliber, open **Settings → Integrations → Claude Code**.
2. Choose the Anthropic API key path.
3. Create an Admin API key in the Anthropic Console and paste it into Caliber.
4. Save. Caliber syncs billed usage, cost, and related roster data permitted by the key.

{% hint style="info" %}
Admin keys are for Console / Enterprise billing-style usage. They are not the same as a personal Claude.ai API key.
{% endhint %}
{% endtab %}

{% tab title="Enterprise: Analytics key" %}
**Who:** Anthropic Enterprise **Primary Owner** (claude.ai Analytics API keys).

1. Open **Settings → Integrations → Claude Code**.
2. Add an Analytics key with scope `read:analytics`.
3. You can use Analytics alongside an Admin key when your plan supports both.

Exact key UI: Anthropic’s analytics API keys page for your organization.
{% endtab %}

{% tab title="Team: station plugin" %}
**Who:** Caliber admin (mint token) + IT / MDM or each user (install).

1. In Caliber, open **Settings → Integrations → Claude Code** and choose the Team / no API key path when prompted.
2. Deploy the Caliber station plugin so usage reaches Caliber from enrolled machines.

Team figures are **device-sourced estimates** (tagged `usage_source=team-edge`), not Anthropic invoice pulls. Coverage depends on how many machines run the plugin. Enterprise API keys provide richer org-wide analytics when you have them.
{% endtab %}
{% endtabs %}

## Related

* Transcript / governance capture is **Caliber Analysis** (part of the station plugin), not the Anthropic Admin key. See [What the bundle includes](/caliber-station-plugin/what-the-bundle-includes.md).
* [Data freshness](/connect-your-providers/data-freshness-and-sync-schedule.md)
* [Access you need to grant](/getting-started/access-you-need-to-grant.md)


---

# 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.trycaliber.ai/connect-your-providers/anthropic-claude.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.