Connector
Anthropic API and Claude Code, in the same dashboard.
One connector covers your Claude API costs (by workspace, by key, by model) and real Claude Code usage, developer by developer.
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 |
|---|---|
| API cost by workspace and by key | Anthropic spend broken down the way your organization is structured. |
| Claude Code usage by developer | Real adoption of the tool, person by person: useful before extending licenses. |
| Cost by model | Priced against the rate card, with currency conversion. |
| Budget, alerts, reconciliation | Monthly budget, thresholds, reconciliation with your Anthropic invoices. |
Setup
What to prepare.
- Who, on your side
- An organization admin in the Anthropic Console.
- Prerequisites
- An Anthropic organization (Console).
- What to provide
- An Admin API key (sk-ant-admin…).
- Where to get it
- Console → Settings → Admin API Keys → Generate Key, permission "organization_read".
Frequently asked questions
Before you start.
- How is this different from the Claude Enterprise connector?
- Two products, two keys. This connector covers the Anthropic API and Claude Code; the Claude Enterprise connector covers your company claude.ai seats. Both can coexist, each keeps its own source.
- Does the key give access to conversations?
- No. The organization read permission exposes usage and billing, 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.