Anthropic · Claude
Every Claude dollar, accounted for.
API usage, Claude Enterprise seats, and Claude Code. One view of what your org spends on Anthropic, and what it produces.
Most tools see the API bill or the seats. Anthropic customers have both, plus Claude Code.
- Spend by team, project, and model, synced from your org chart
- Cost per output: spend tied to work actually delivered
- ROI you can defend at the Anthropic renewal
We’ll reach out at the email you provided.
TRUSTED BY AI-FORWARD ENTERPRISES
THE WHOLE STACK
Start with Claude. Measure everything.
Larridin measures AI spend across every vendor your org runs: Claude beside OpenAI, Gemini, Cursor, and Copilot, plus cloud-billed usage and the agents you built in-house.
- Every vendor, seat, and agent in one spend model
- Attributed by team, department, and use case
- One ROI number across the stack
EVERY VENDOR, ONE SPEND MODEL
Claude is one column in the ledger. The same spend model covers every AI vendor, seat, and agent your org runs, attributed by team, department, and use case.
HOW IT ADDS UP
However your org buys AI, the spend lands in one place.
Consolidated first, then owned, then tied to output. The spreadsheet retires.
CONSOLIDATE
The whole AI bill, reconciled
Seats from procurement, API from the Console, Claude Code from developer tooling, cloud-billed usage from AWS and GCP: one spend model across the stack.
ATTRIBUTE
Each dollar gets an owner
Anthropic’s usage API has no per-user dimension, and every vendor has its own version of that ceiling. Larridin maps them all to teams, departments, and use cases from your org chart.
PROVE ROI
Spend meets the work it paid for
Cost per output, hours returned, adoption: measured from PRs and tickets, ready for the budget review.
FULL CLAUDE COVERAGE
Cowork sessions and Claude Tag usage land in the same ledger as API and seats, attributed to the same teams. New Claude surfaces show up the day your org adopts them.
WHAT IT PRODUCED
Claude spend, tied to work delivered.
Cost per PR, hours returned, and adoption, measured from the work itself. The renewal conversation starts with a number.
- Cost per output for API, seats, and Claude Code
- Hours returned, counted from PRs, tickets, and reports
- Adoption trends by team and workflow
Claude ROITHE ANTHROPIC LEDGER
Every Claude surface, one ledger.
API, Claude Code, and Enterprise seats reconciled, then allocated by team, project, and cost center.
Anthropic SpendAll your AI spend, Claude and beyond, in one place. Attributed by team, department, and use case.
We’ll reach out at the email you provided.
SEAT UTILIZATION
Who’s active, who’s not, what to reclaim.
Claude Enterprise seats measured by actual use: cost per active user, with dormant seats flagged before the renewal.
- Active vs. dormant, from real usage
- Cost per active user, by team
- Reclaim list ready at renewal
ONE VIEW
Take one screen into the Anthropic renewal.
Every vendor’s spend, next to the work it produced. Claude in context.
Output attribution. Work delivered across the stack, measured from the systems it lands in, beside what it cost.
Every vendor, one column each. Claude sits beside OpenAI, Cursor, and Copilot, so the renewal conversation covers the whole stack.
Claude in context. The vendor you came to track, measured against everything else you run.
HOW IT CONNECTS
Connected in a day.
Connect Anthropic
Authorize Larridin against Anthropic’s Admin and usage/cost APIs. Nothing in your codebase changes.
Allocation syncs
Teams and cost centers come from your org chart. Every seat, token, and Claude Code session rolls up automatically.
Output attaches
Work delivered with Claude lands next to what it cost: cost per output from the first scan.
FAQ
Questions Anthropic customers ask us.
How does Larridin ingest Anthropic spend?
Through Anthropic’s reporting APIs: the usage and cost APIs and Claude Code analytics on the API side, and the Enterprise analytics API for seats. Different credentials, one ledger, no manual exports.
Why is consolidating Claude spend hard?
Because it lives in different systems: seat invoices in procurement, API usage in the Console, Claude Code in developer tooling, Bedrock and Vertex buried inside cloud bills. Larridin reads each source and reconciles them into one spend model that adds up to what finance actually pays.
Does it cover Claude Code and Cowork?
Yes. Per-developer Claude Code spend, Cowork sessions, and Claude Tag usage are tracked alongside API and seat costs. Note the Claude Tag split: channel usage bills the org, while DMs bill the employee’s personal account, so the org invoice is not the whole picture.
What about Claude on Bedrock or Vertex?
Covered. Cloud-hosted Claude doesn’t appear in Anthropic’s reporting APIs, so Larridin reads it from your AWS and Google Cloud billing exports and attributes it the same way as direct API spend.
Can spend be allocated without tagging every request?
Yes. Allocation comes from your org chart and workspace structure, not per-request tags. Whatever can’t be mapped is flagged as unattributed, never silently dropped.
How is this different from Anthropic’s own dashboard?
The Console shows usage. Larridin shows allocation and return: spend by team and cost center, seat utilization, and the work the spend produced. And the same ledger covers your other AI vendors, so you can see Claude beside everything else you run.
CHEAP TOKENS AREN’T THE GOAL
Useful ones are.
Optimize cost per outcome.
Larridin ties model spend to the work it produced, so you optimize for cost per outcome, not cost per token.
We’ll reach out at the email you provided.
SOC 2 Type II · GDPR ready · 30 minutes on your data