Anthropic

The Anthropic connector imports organization-level cost and usage from the Anthropic Admin API.

It reads two feeds:

  • The cost report — what you were actually charged, broken down by workspace and meter. Dashboard spend comes from the cost report.
  • The usage report — how many tokens each workspace, API key and model consumed. Token counts and the per-key/per-model breakdown come from this.

The cost report shows the total charged per workspace, model and day, but not which API key was responsible — Cloud Ctrl shares each day's charge across the API keys that were active in the workspace, so heavier keys carry more of the cost. Shares always add back up to exactly what Anthropic billed, so your total spend matches your Anthropic invoice.

Experimental

The Anthropic Admin reporting API is still maturing, so the data shape and how usage is attributed may change as the API evolves. Treat the figures as indicative rather than audited.

Get an Admin API key

  1. Sign in to the Anthropic Console as an organization Admin (Owner).
  2. Open Settings → Admin keys.
  3. Create an Admin API key (it starts with sk-ant-admin-) with organization read access, so Cloud Ctrl can read the Cost and Usage Report APIs.
  4. Copy the key — it is only shown once.

Warning

Standard API keys cannot read the organization reports — only an Admin key works.

Add a Credential

  1. Open Settings → Cloud Connections → Anthropic
  2. Click + Add Credential
  3. Enter a display name and paste the Admin API key
  4. Click Submit

Add a Cloud Account

  1. From Settings → Cloud Connections → Anthropic, click + Add Cloud Account
  2. Select the credential you just added
  3. Optionally enter an Organization ID — the Admin key is already scoped to a single organization, so this is only needed if the key has access to multiple organizations
  4. Click Submit

Once connected, the initial import pulls up to 90 days of history (configurable on the cloud account), then imports month by month. Your data can take up to 24 hours to complete the initial import.

Attribution notes

  • Workspace attribution — the workspace is Anthropic's primary allocation handle (the equivalent of a project or team). To see spend by workspace, make your API calls within a specific Anthropic Workspace (use workspace-scoped API keys). Calls not tied to a workspace show as unattributed. If all your spend shows as unattributed by workspace, this is the fix.
  • No user attribution — Anthropic's reporting API does not expose which user made a request, only the workspace and API key. Spend by person is therefore not available for Anthropic; use API key names to distinguish workloads or teams.
  • Cost centre and repository — Anthropic does not provide these. Use Tag Mapping to map your workspaces to the cost centres or repositories you use elsewhere in Cloud Ctrl.
  • Allowance vs on-demand — the cost report exposes only the metered amount actually billed; credits and commitments are applied at the invoice layer. Every token Cloud Ctrl sees is recorded as on-demand, and the charge-mix breakdown will show Anthropic usage as on-demand rather than included.