API Key Setup Guide¶
Start with your plan — it decides which keys exist at all. Availability below is taken from the official Anthropic documentation (Analytics APIs, Claude Code analytics):
| Your plan | API keys available | What to do in this application |
|---|---|---|
| Claude Team plan (claude.ai) | None. The Analytics API is Enterprise-only — the official docs state “The API is not available on the Teams plan” — and the Admin / Claude Code Analytics / Usage & Cost APIs belong to Claude Console (API) organizations. | Select Team plan under Settings → API Connections → Organization plan, leave both key fields empty, and import the two official exports (see Team plan without keys below). |
| Claude Enterprise plan (claude.ai) | Analytics API key (primary owner) | Create the key, add it, test the connection. |
| Claude Console / API organization | Admin API key (sk-ant-admin01-…) |
Create the key, add it, test the connection. |
| Team or Enterprise plus a Console org | As above, per organization | Add every key you have — capability detection records which key serves which category. |
The application uses up to two different, non-interchangeable key types. Configure whichever your organization has — capability detection adapts to what the keys can serve. All access is read-only.
| Key | Serves | Created in | Who can create it |
|---|---|---|---|
| Analytics API key | Claude Enterprise Analytics API: org activity summaries, per-user activity (chat / Claude Code / Cowork / Design / Office / Science), skills & connectors, org + per-user token usage and cost | claude.ai → Organization settings → API (claude.ai/admin-settings/api-access) |
Primary Owner of the Claude Enterprise org — the option does not exist on the Team plan |
Admin API key (sk-ant-admin01-…) |
Admin API: organization users & invites, Claude Code Analytics (per-user daily productivity + per-model cost), Usage & Cost reports (Claude Console orgs) | Claude Console → Settings → Admin keys (platform.claude.com/settings/admin-keys) |
Organization admin of the Claude Console org |
An Admin key cannot call the Enterprise Analytics endpoints and an Analytics key cannot call the Admin endpoints. If you have both products, add both keys.
Team plan — running entirely on official exports¶
On the Team plan there is no key to create; that is Anthropic's plan design, not a limitation of this application, and the application fully supports running this way:
- In Settings → API Connections, set Organization plan to Claude Team plan. Capability rows then explain why API categories are unavailable and point to the import path instead of asking for keys.
- Export from claude.ai (Admins/Owners):
- Members analytics —
claude.ai/admin-settings/members→ Analytics → export the period. Start with this one: it is a single file covering every member for the whole window, with seat tier, last-active date, days active and per-product activity (Chat, Claude Code and Cowork). Import it with the claude.ai members analytics export profile — the reporting window is read from the file name, so keep the name claude.ai gives it. - Claude Code analytics export —
claude.ai/analytics/claude-code→ leaderboard → Export all users (per-user Claude Code contribution data; enable the analytics feature underclaude.ai/admin-settings/claude-codefirst). - Spend report — your organization's analytics settings; lists token usage and estimated usage-credit spend per user and per model.
- Import both on Sync & Audit → Official export imports, choosing the matching profile (Claude Code daily usage export and claude.ai spend report). The preview shows exactly how columns were mapped — adjust the mapping there if your export's headers differ.
- Maintain the member directory with the Organization members export
profile (a CSV of email/name/role/status — export or assemble it from
claude.ai/admin-settings/members).
Want an answer before installing anything?
Drop the same exports into the Usage analyzer — it runs the identical scoring and threshold logic in your browser (nothing is uploaded), so you can see the result and tune your minimum-usage criteria first.
Everything downstream — dashboards, Weighted Usage Index, alerts, exemptions and all seven report formats — works identically on imported data. Categories the exports do not cover (for example chat message counts) are shown as Unavailable / No Data and are excluded from the scoring denominator, never counted as zero.
Step 1 — Create the key(s)¶
Analytics API key (Claude Enterprise plan only — not offered on Team)
1. Sign in to claude.ai as the organization's primary owner.
2. Open Organization settings → API and enable API access.
3. Create an Analytics API key (scope read:analytics) and copy the
secret immediately — it is shown only once.
Admin API key (Claude Console / API organizations)
1. Sign in to the Claude Console as an organization admin.
2. Open Settings → Admin keys.
3. Create a key and copy the sk-ant-admin01-… secret.
Step 2 — Add the key(s) securely¶
- Launch the application → Settings → API Connections.
- Paste each key into its field and click Save key.
- Keys are written to the Windows Credential Manager
(service
ClaudeOrgUsageMonitor) — never to files, the database, logs or exports. The UI only ever shows a masked form (************xxxx). - Click Test connection & detect capabilities.
- The connected organization, key validity and every data category's availability (with the exact reason when unavailable) are displayed and recorded.
Step 3 — Understand what your plan provides¶
Typical outcomes:
- Claude Team plan, no keys — API sync is not available on this plan; every capability row says so explicitly (with the import path to use). All data arrives through the official export imports above.
- Claude Enterprise org, Analytics key only — everything except the Admin-key Claude Code Analytics endpoint (per-user Claude Code activity still arrives via the Analytics API). Roles/invites may be limited; the directory is then derived from activity records.
- Claude Console org, Admin key only — users & invites, Claude Code Analytics, org token usage & cost. claude.ai chat analytics are not available on this key: import official CSV exports for chat data (Sync & Audit → Official export imports).
- Both keys — full coverage; the app automatically prefers the richer source per category and records which source served each category.
Categories your plan does not provide are always displayed as Unavailable (never as zero usage) and are excluded from the Weighted Usage Index denominator.
Key hygiene¶
- Rotate keys periodically; paste the new key over the old one (Save key)
and re-test. Removing a key (
Remove) deletes it from the Credential Manager. - Grant keys to as few people as possible; this tool needs no other scopes.
- If a key is ever exposed, revoke it in the console where it was created.