Connecting Anthropic Spend Data to TeamOhana: Instructions & FAQ

Last updated: November 5, 2026

Connecting Anthropic to AI Spend lets TeamOhana read your Anthropic billing and usage data so it can show up, attributed to people and agents, in your AI Spend dashboard. Depending on how your organization uses Anthropic, you'll connect one or both of two separate keys: a Claude Console Admin API key for direct API usage, and a Claude Enterprise Analytics API key for Claude Enterprise seats. Neither key gives TeamOhana access to prompts, completions, files, or code.

Prerequisites

  • TeamOhana role and permission: Admin or IT Admin, with the Manage AI Providers permission.

  • Access in Anthropic: To create a Claude Console Admin key, you need the Admin, Owner, or Primary Owner role in your Anthropic Console organization. To create a Claude Enterprise Analytics key, you need to be the Primary Owner of your Claude Enterprise organization.

  • Plan tier: Not applicable — this integration is available on all TeamOhana plans.

  • Which key(s) you need: If your company uses the Anthropic API directly (agents, internal tools, developers with API keys), you need the Console Admin key. If your team has Claude Enterprise seats (Claude chat, Claude Code, Cowork), you need the Enterprise Analytics key. Many organizations need both.

Setup Steps

From the left nav, go to Settings > Integration to connect your AI providers. 

Part 1 — Claude Console Admin API key

  1. Sign in to the Claude Console.

  2. Go to Settings > Admin keys (or API keys > Admin keys).

  3. Click Create key.

  4. Name it teamohana-spend-readonly so it's easy to audit and revoke later.

  5. Set an expiration date. We recommend 12 months; you'll be reminded before renewal.

  6. Click Create and copy the key. It starts with sk-ant-admin01-.

  7. Share the key with TeamOhana through your secure onboarding channel.

Important: Do not send API keys over email or Slack. Always share credentials through the secure channel provided during onboarding.

TeamOhana uses this key to call read-only reporting endpoints on a daily schedule: daily spend, token usage, per-developer Claude Code cost estimates, and API key names (used to map spend to teams and agents — never key secrets, which Anthropic does not expose).

Part 2 — Claude Enterprise Analytics API key

  1. Sign in to Claude with the Primary Owner account.

  2. Go to Organization settings > API.

  3. If the Analytics API isn't enabled yet, enable it (a one-time toggle).

  4. Click + Create key.

  5. Name it teamohana-analytics-readonly.

  6. Under scopes, check only:

    • read:analytics (required — lets TeamOhana read per-seat usage and cost, so the dashboard shows real spend per person rather than just the flat seat fee)

    • read:spend_limits (optional — lets TeamOhana show each member's spend limit and month-to-date extra usage)

  7. Create the key and copy it.

  8. Share it with TeamOhana through your secure onboarding channel.

Important: Do not select any write:* scopes or compliance scopes. TeamOhana never needs them, and the key cannot do more than the scopes selected at creation — scopes cannot be changed later.

Part 3 — Seat pricing

Anthropic does not expose your negotiated seat price through any API. To calculate fully-loaded per-person cost, share your per-seat monthly price(s) from your Anthropic order form, along with your billing cycle (annual or monthly), with your TeamOhana contact.

[Optional] Permissions Reference

Key

Required scopes

What it can read

Claude Console Admin key

Full Admin API (not independently scopeable)

Billing totals, token counts, key/workspace/member metadata. No content.

Claude Enterprise Analytics key

read:analytics, optionally read:spend_limits

Aggregated usage metrics and per-user cost totals. No content, no member management.

Note: Anthropic does not currently offer a scoped or read-only Admin key for Claude Console organizations — every Console Admin key carries the full Admin API. TeamOhana limits risk with key expiration, a dedicated named key, minimal endpoint usage, and your ability to revoke access unilaterally at any time.

Troubleshooting

  • Worried about what the Console Admin key can do? It cannot read conversations, prompts, files, or code. It cannot create new API keys or run inference — Anthropic's Admin API can only list and update existing keys, and the inference API rejects Admin keys outright. In the worst case of a leaked key, the practical risk is disruption (deactivated keys, membership changes), not data exfiltration, and you can revoke it at any time.

  • Want to revoke access? For the Console key, go to Settings > Admin keys and deactivate teamohana-spend-readonly. For the Enterprise key, go to Organization settings > API and delete teamohana-analytics-readonly. Revoking only stops future syncs — your historical dashboard data remains.

  • Not sure which key(s) you need? See the "Which key(s) you need" prerequisite above, or contact your TeamOhana representative.

Related Resources