claude.ai Enterprise cost per user
Import per-user Claude Enterprise cost with an Analytics API key, and allocate seats and usage to teams.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
Monthly, after Anthropic analytics refresh.
Context used
Remembered
Costory investigates
01
Connect Claude AI
A primary-owner Analytics API key with read:analytics.
02
Per-user cost
Costory imports Claude Enterprise per-user cost.
03
Map to teams
Users to departments or teams.
04
Report
A monthly per-team breakdown.
Where you see it
Claude
You decide
IT and finance decide on seat allocation.
Why it matters
AI assistant seats spread across the company. Finance asks who uses them and which teams should carry the cost.
Who it’s for
IT, finance, engineering managers
Where it runs
Claude · Slack
What you get
What lands in front of your team
Per-user cost
From Anthropic's analytics.
Team allocation
Seats charged to the right budget.
Next to API spend
Enterprise and API in one view.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
FAQ
Questions about this playbook
Which AI providers can Costory import?
OpenAI, Anthropic (API and claude.ai Enterprise), Azure OpenAI, AWS Bedrock, Google Vertex AI, OpenRouter, Cursor, ElevenLabs, Kling AI and BytePlus.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
Monthly, or when a team's AI coding spend jumps.
Cursor and Claude Code spend per developer
Track AI coding tool spend per user and per model, from Cursor and the Anthropic Claude Code connector, next to the rest of your cloud.
See the playbook
Costory notices
Every Monday, across every AI provider.
All AI spend in one view: OpenAI, Anthropic, Bedrock, Vertex AI and more
The agent tracks total AI spend across model APIs, cloud AI services and AI tools, and reports the weekly trend in one place.
See the playbook
Costory notices
Daily, as LLM provider costs refresh.
LLM cost allocation by team, feature and customer
Allocate model spend from OpenAI, Anthropic, Azure OpenAI, Bedrock, Vertex AI and OpenRouter to teams, features and customers.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud