Four ways to feed the dashboard: the Anthropic Admin key (nothing to install, attribution per developer), the CLI on laptops (per-session detail, also works for individual Pro and Max accounts), the OpenAI Admin key for the organisation's OpenAI API usage, and the OpenRouter management key for everything routed through OpenRouter.
Read-only screen, shown on the demo's sample organisation.
One Admin key from your Anthropic Console covers Claude Code usage on subscription seats per developer (30 days of history) and the organisation's API usage, with nothing to install on laptops.
Claude Code on subscription seats, per developer, and the organisation's API usage. API-billed Claude Code arrives with the API usage, on one collective line per key: the Admin key does not say who used it, the CLI on laptops does. Claude.ai chat is not covered: no API exposes its token counts, except on a usage-billed Enterprise plan. Bedrock, Vertex and sessions started from a personal account are not tracked.
Syncs every hour · last run 40 min ago, next around 23:10 UTC. Claude Code per member · final through 5 Oct, the last two days fill in on every run.
Read-only demo. In your workspace, you paste the Admin key and the first import runs right after.
You only need an Admin key from your OpenAI organisation: API usage syncs every hour, attributed per member when the API allows it, with the rest on a shared line.
OpenAI API (platform), completions endpoints. ChatGPT Team/Enterprise and embeddings are not covered yet.
Syncs every hour · last run 25 min ago, next around 23:10 UTC.
Read-only demo. The sample organisation's OpenAI usage comes from Codex run on an API key, so it is counted with the OpenAI API. In your workspace, you paste the OpenAI Admin key and usage then comes in every hour.
With a management key from your OpenRouter account, usage of every model called through your OpenRouter keys comes in daily (yesterday's figures, consolidated), attributed per person, with the actual provider of each model.
Everything that goes through your OpenRouter keys, attributed per member. Cache writes count as input. BYOK rows from a provider already connected here are ignored. Usage from Claude Code or an SDK pointed at OpenRouter is also counted on the CLI or SDK side; the two are not reconciled yet.
Data complete through 6 Oct 23:59 UTC · next run around 00:20 UTC.
Read-only demo. Here the Data team goes through OpenRouter for Gemini, Llama and DeepSeek. In your workspace, one OpenRouter management key is enough: yesterday's usage comes in daily, linked to each model's actual provider.
Each developer installs it with a one-line command and an invitation code specific to your organisation. Local sessions are then reported with detail per session and per project, including individual Claude Pro and Max accounts.
On push · last session 3 h ago.
This demo runs on sample data. We set this dashboard up on your real data during the engagement, with a monthly review of the figures.
Book 30 minutes →