Connector
Claude Enterprise: seats, adoption, cost per user.
The Analytics key of your claude.ai organization is enough: optidome tracks assigned seats, real adoption per user and the corresponding cost.
Connection through the official admin API, read-only: optidome never modifies the configuration of your tools.
What optidome measures
The data collected, as is.
| Data | Detail |
|---|---|
| Seats and invitations | Assigned seats, pending invitations: the full universe of what you pay for. |
| Adoption per user | Who uses their seat, who never activated it: dormancy, priced. |
| Cost per user | Cost attributed to each user, reconciled with your billing. |
Setup
What to prepare.
- Who, on your side
- The primary owner of the claude.ai organization.
- Prerequisites
- A Claude Enterprise plan.
- What to provide
- The Analytics key (scope "read:analytics").
- Where to get it
- claude.ai → Organization settings → API. The section is only visible to the primary owner.
Frequently asked questions
Before you start.
- Is this the same key as the Anthropic connector?
- No. The claude.ai Analytics key and the Anthropic Console Admin API key are two distinct keys. Both connectors coexist: one tracks claude.ai seats, the other the API and Claude Code.
- What does optidome see of the conversations?
- Nothing. The Analytics API exposes adoption and cost measures per user, never the content of exchanges.
Private beta. Access is by application, and the setup of your first connector is assisted: shared screen, until the first data lands.