Anthropic (Claude)

The Anthropic connector reads Claude usage from the Anthropic Admin API: members, workspaces and API keys, plus usage and cost reports by model, workspace and key. For Claude Enterprise plans with compliance access, it also ingests conversation data for detection and topic analysis.

Set up

1. An organization admin creates an Admin API key (sk-ant-admin…) in the Claude Console.
2. Add the connector:

promptglass connectors add anthropic \
  --admin-key-env ANTHROPIC_ADMIN_KEY \
  --backfill 90d

Data collected

Data	Endpoint family	Use
Members and roles	Admin API: users, invites	Seat utilization, joiner/leaver hygiene
Workspaces and API keys	Admin API: workspaces, api_keys	Owner mapping, key inventory
Token usage by model/workspace/key	Usage & cost report	Spend by team, model right-sizing
Cost	Cost report	Budget tracking
Conversations (Enterprise with compliance access)	Compliance export	Detection, efficiency, topics

Claude Code and the Claude desktop app

Developers using Claude Code with an organization API key appear in usage reports under that key. For per-user attribution and inline DLP on code and secrets, set ANTHROPIC_BASE_URL to the gateway in API mode on developer machines (or push it with the endpoint agent). Claude Desktop and claude.ai are covered by the browser extension and the forward proxy.

Mapping

Map each Anthropic workspace to a team and cost center under Connectors → Anthropic → Mapping. Keys created after the mapping inherit the workspace’s mapping automatically.