Skip to main content
This is the recommended way to connect Claude. If you use the Anthropic Console or API instead, see Claude Platform.

​
What you’ll accomplish

  • Connect with your claude.ai Analytics API key and Compliance API key
  • Track billed Claude spend over time, by model, by department, and per person
  • See every Claude seat, including people who have access but no usage (the seats you may be paying for and not using)
  • Identify top users and the teams driving usage
  • Get per-person totals that reconcile to your Anthropic bill
  • Optionally, add an Admin API key to see and update each person’s spend limit

​
What June syncs

From your Claude Enterprise account, June syncs:
  • Billed spend per person, across all Claude products (chat, Code, and more)
  • Token usage per person
  • Per-person engagement: sessions, conversations, and coding output (pull requests, commits) per person per day, split by product
  • Skill usage: which skills your team uses, how often, and the spend attributed to each
  • Your member roster, so June can show every seat, including people with no usage
  • Per-person spend limits (optional, with an Admin API key), so you can compare each person’s cap against what they actually spend
Because every figure is billed and attributed to a person, your per-person and per-department totals reconcile to your Anthropic invoice. Usage history is available from January 2026 onward and refreshes daily.
Claude Enterprise uses two required keys. The Analytics key reads your spend and usage. The Compliance key reads your member roster, so June can show every seat, including unused ones. A third key, the Admin API key, is optional: it lets June show each person’s spend limit beside their actual spend, and update a limit when an admin approves a change. Without it, everything else works. You just won’t see limits.

​
Capabilities

June ingests usage and billing data from Anthropic. With the optional Admin API key, the only action it can take is updating a spend limit when an admin approves the change in June.

​
What each key is for

June only reads your member directory with the Compliance key: who is in the organization and which groups they belong to. It never requests conversation content.

​
Prerequisites

Before starting, ensure you have:
  • A Claude Enterprise (claude.ai) plan, with the Compliance API enabled for your organization
  • Primary Owner access to generate API keys

​
Connect Claude Enterprise

1

Generate an Analytics API key

  1. Sign in to claude.ai as a Primary Owner.
  2. Go to Analytics → API keys.
  3. Create a new key and copy it. This is your Analytics API key (it carries the read:analytics scope by default).
2

Generate a Compliance API key

This key lets June read your member roster, so it can show every seat (including unused ones).
  1. Go to Organization settings → API and create a key.
  2. Select the read:compliance_user_data and read:compliance_org_data scopes, and copy it. This is your Compliance API key.
  3. If those scopes aren’t available, your organization needs the Compliance API enabled first. Request it from Anthropic, then create the key.
3

(Optional) Generate an Admin API key

This key lets June show each person’s spend limit and update it when an admin approves a change. Skip it if you don’t use spend limits.
  1. Sign in to the Anthropic Console as an admin.
  2. Go to Settings → Admin keys and create a key (it starts with sk-ant-admin).
  3. Copy it. This is your Admin API key.
4

Add the integration in June

  1. In June, open the Integrations page.
  2. Choose Claude Enterprise.
  3. Paste your Analytics API key and your Compliance API key (and the Admin API key, if you created one), then save.
5

Wait for the first sync

June backfills your historical usage and refreshes daily. Spend, per-person data, and seats appear under AI usage → Claude once the first sync completes.