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

# Anthropic

> Connect Parable to Anthropic Claude Admin and Compliance APIs

<img className="connector-logo" src="https://img.logo.dev/anthropic.com" alt="Anthropic logo" />

# Anthropic Connectors

Connect Parable to Anthropic for organization administration, usage and cost reporting, or Enterprise compliance audit data.

<CardGroup cols={2}>
  <Card title="Claude Admin" icon="chart-line" href="/connectors/anthropic/claude/admin-api-key/setup">
    Admin API key for users, workspaces, API keys, and usage/cost reports
  </Card>

  <Card title="Claude Compliance" icon="shield" href="/connectors/anthropic/claude-compliance/compliance-key/setup">
    Compliance Access Key for audit activity and optional content metadata
  </Card>
</CardGroup>

## Which connector should I use?

| Need                                                  | Connector             | Key type                                   |
| ----------------------------------------------------- | --------------------- | ------------------------------------------ |
| Token usage and daily cost reporting                  | **Claude Admin**      | Admin API Key (`sk-ant-admin01-...`)       |
| Org directory, workspaces, invites, API key inventory | **Claude Admin**      | Admin API Key                              |
| Compliance activity feed and org directory            | **Claude Compliance** | Compliance Access Key (`sk-ant-api01-...`) |
| Chat and project metadata for eDiscovery              | **Claude Compliance** | Compliance Access Key                      |

These connectors use **different keys and API surfaces**. An Admin API Key cannot replace a Compliance Access Key for full compliance data, and a Compliance Access Key does not provide Admin usage/cost report endpoints.