anthropic_admin
Manage Anthropic organization members, invites, workspaces, workspace members, API keys, usage and cost reports, Claude Code analytics and rate limits using SQL.
For the user/inference surface (messages, models, batches, files, agents, sessions, skills, memory stores, vaults) use the anthropic provider — it authenticates with a separate, workspace-scoped API key.
total services: 6 total resources: 17
See also: [SHOW] [DESCRIBE] [REGISTRY]
Installation
REGISTRY PULL anthropic_admin;
Authentication
The anthropic_admin provider authenticates with an org-scoped Admin API key (sk-ant-admin01-...) sent in the x-api-key header. Set the following environment variable:
ANTHROPIC_ADMIN_KEY- an Admin API key, created in Claude Console > Settings > Admin keys
Only organization members with the admin role can provision Admin API keys, and the Admin API is unavailable for individual (non-organization) accounts. Admin keys and regular Claude API keys are disjoint: neither can call the other's endpoints. The required anthropic-version header is sent automatically (default 2023-06-01).
On the Claude Platform on AWS only the workspace endpoints (create, get, list, update, archive) are available; organization members, invites, API keys, reports and rate limits are not.
Coverage
The full Admin API surface is exposed, except the following documented exclusions:
- Workload Identity Federation endpoints (service accounts, federation issuers, federation rules) — these reject Admin API keys and require an
org:adminOAuth token - Compliance API, Spend Limits API and Claude Enterprise Analytics — these use a third key type (
sk-ant-api01-..., Claude Enterprise) and belong in a futureanthropic_enterpriseprovider