Pacia Intelligence

AI integration

Claude Code and Pacia

Pacia supports both Anthropic organisation analytics products, and they are genuinely different. Pacia detects which key type you have entered, validates it against the matching endpoint, and reports only what that endpoint actually exposes.

Talk to us

What Pacia reads from Claude Code

  • Claude Console: Claude Code usage and estimated cost, via an Admin API key

  • Claude Enterprise: seats, daily active users, sessions, accepted and rejected tool actions, lines changed, commits and pull requests, via an Analytics API key with read:analytics

Connecting it

  1. Create the right key 3 min

    For a Console organisation, an Admin API key from platform.claude.com organisation settings. For an Enterprise organisation, an Analytics API key from claude.ai under Organization settings → API with read:analytics granted.

  2. Enter it in AI Adoption → Providers 1 min

    Pacia detects the key type, validates it against the matching Anthropic endpoint and encrypts it at rest.

Limits, stated up front

Every integration page on this site lists what the integration does not do. Finding that out during a trial is worse for both of us than finding it out now.

  • The Enterprise activity API does not report cost, so Pacia leaves cost empty rather than estimating it.

  • Console data can lag by about an hour; Enterprise data lags longer, so Pacia syncs through three days before the current date rather than showing a half-populated today as a real drop.

  • Anthropic’s organisation APIs do not include Claude usage hosted through Amazon Bedrock, Google Vertex AI or Microsoft Foundry.

  • Never send an analytics key by email or chat. Enter it only in the provider password field.

What this unlocks

Connect Claude Code and see your own data

Talk to us