StackSpend is a cloud and AI cost management platform that connects to AWS, GCP (Google Cloud), Azure, Vercel, OpenAI, Anthropic, Claude, Cursor, GitHub, Hugging Face, Twilio, Grok (xAI), Snowflake, and ClickHouse Cloud. For Claude, StackSpend provides read-only cost monitoring, daily Slack or email reports, anomaly alerts, forecasting, and setup guidance. StackSpend receives Claude OpenTelemetry from Claude Code, Cowork, and Office agents. See estimated daily cost, user-level attribution, model breakdowns, anomaly detection, and budget tracking alongside your other AI and cloud providers. Claude telemetry is a token-based estimate, not an official Anthropic invoice: it is derived from usage events and does not factor in subscription (plan) pricing, so treat it as a directional signal rather than a billed amount. Historical 90-day backfill is not available — telemetry is captured from setup time forward.
Claude logo
Claude

Track Claude Code, Cowork, and Office agent usage from OpenTelemetry in one daily view.

StackSpend receives Claude OpenTelemetry from Claude Code, Cowork, and Office agents. See estimated daily cost, user-level attribution, model breakdowns, anomaly detection, and budget tracking alongside your other AI and cloud providers. Claude telemetry is a token-based estimate, not an official Anthropic invoice: it is derived from usage events and does not factor in subscription (plan) pricing, so treat it as a directional signal rather than a billed amount. Historical 90-day backfill is not available — telemetry is captured from setup time forward.

Start free trialView setup guide
Read-only access·14-day free trial·No credit card required·Setup in under 5 minutes
See it in action

See spend against budget, every day.

The same burn-up view your dashboard shows: cumulative spend against budget, with a forecast tail so you know where the month ends before it does.

The problem

Why Claude spend is hard to control

01

Claude usage can happen across developer tools, Cowork, and Office agents. Without one collector, teams cannot see where usage is coming from or which users and sessions are driving cost.

02

Claude OpenTelemetry includes many event types. Cost signals, token usage, tool events, and logs need normalization and deduplication before they are useful for finance or operations.

03

Claude sits alongside Anthropic API, OpenAI, Cursor, and cloud providers. Reviewing each source separately makes total AI spend hard to explain.

The solution

What StackSpend shows for Claude

  • StackSpend gives each Claude provider connection a scoped ingest key and copy-ready OpenTelemetry settings for Claude Code, Cowork, and Office agents.

  • Claude telemetry is normalized into daily cost rows with user, model, session, and source attribution so teams can separate Claude Code, Cowork, and Office agent usage.

  • Daily alerts, anomaly detection, budgets, and pace-to-forecast help teams spot unexpected Claude usage before the month closes.

Exactly what we track

Setup guide
Claude Code OpenTelemetryClaude Cowork OpenTelemetryClaude Office agents OpenTelemetryEstimated cost by modelUser and session attributionDaily spend and anomaly detectionForward-looking telemetry from setup time, not 90-day backfill
Monitoring scope

What Claude cost monitoring tool covers

These are the details teams usually need when comparing native billing screens with a dedicated monitoring layer.

Tracks Claude Code, Cowork, and Office agent telemetry through OTLP ingest.

Separates estimated cost-bearing events from noisy logs and non-cost usage signals.

Uses a scoped provider ingest key rather than Anthropic API billing credentials.

Failure modes

What typically causes Claude costs to spike

A managed Claude Code rollout expands to more developers without a matching daily usage signal

Cowork or Office agent sessions start sending more Opus requests than expected

A long-running Claude session produces repeated high-cost model calls during a refactor

Telemetry includes both logs and metrics and needs deduplication before costs are trusted

Claude admin monitoring and Anthropic billing views vs StackSpend

Why teams move beyond native Claude billing

Claude admin monitoring and Anthropic billing views is built for investigation. StackSpend is built for prevention.

Claude admin monitoring and Anthropic billing views

  • Telemetry setup is separate from cost reporting and needs collector configuration
  • Raw OpenTelemetry events include noisy non-cost logs that are hard to read directly
  • No unified view with OpenAI, Cursor, cloud, and other AI providers
  • Estimated Claude tool usage is not automatically translated into daily budget signals

StackSpend

  • Copy-ready Claude Code managed settings and Cowork/Office OpenTelemetry fields
  • Normalized estimated cost rows with source tagging and deduplication
  • User, model, and session breakdowns in the same dashboard as other providers
  • Daily alerts, anomaly detection, and budget pacing for Claude usage
From day one

What you get when you connect Claude

Access model

OpenTelemetry ingest with a scoped usage:write provider key.

Visibility

Estimated cost by Claude source, user, model, and session.

Coverage

Claude Code, Cowork, and Office agents in one provider connection.

Signals

Daily alerts, anomaly detection, and budget tracking for Claude usage.

Best for

Who should use StackSpend for Claude

  • Product and engineering teams that need model-level visibility before AI bills surprise them.
  • Buyers consolidating OpenAI, Anthropic, Claude, Cursor, or open-model spend into one operating view.
  • Teams that need alerts and forecasting, not just retrospective usage dashboards.
Evaluation checklist
1

Start a trial

Open a StackSpend workspace and add Claude as a provider connection.

2

Copy the Claude setup

Generate the provider ingest key and paste the managed settings or OTLP fields into Claude admin.

3

Send a test event

Start a new Claude session, run a small task, and confirm Last Logs updates on the provider page.

Related reading

Claude setup guideModern startup stack cost systemCursor vs Claude Code vs GitHub Copilot costModern Startup Stack Cost SystemCursor Vs Claude Code Vs Github Copilot Cost 2026How To Monitor AI Developer Spend By User Team ProviderLLM Spend Management Openai Anthropic Cursor

Related

Claude Usage MonitoringClaude Spend AlertsAnthropic Cost MonitoringAI / LLM Cost MonitoringCursor Cost Monitoring
Questions

Frequently asked

How do I monitor Claude Code, Cowork, and Office agent costs?
StackSpend receives OpenTelemetry from Claude Code, Cowork, and Office agents through a scoped ingest key, then normalizes it into daily cost rows with user, model, session, and source attribution. This is a token-based estimate derived from usage events — a directional signal, not an official Anthropic invoice, and it does not factor in subscription pricing. Telemetry is captured from setup forward; 90-day backfill is not available.
How do I connect Claude telemetry to StackSpend?
Create a Claude provider connection in StackSpend to get a scoped ingest key and copy-ready OpenTelemetry settings for Claude Code, Cowork, and Office agents. Point your collector at those settings and StackSpend deduplicates and normalizes the events into daily cost. The ingest is receive-only — StackSpend reads telemetry and never writes back to your Claude environment.
How do I see which user or model is driving Claude usage?
StackSpend attributes Claude telemetry by user, session, model, and source, so you can separate Claude Code, Cowork, and Office agent usage and see who and which model is driving estimated cost. When a managed rollout expands or a session sends more Opus requests than expected, the daily view shows the shift instead of blending it into one total.
Why did my estimated Claude cost jump?
Estimated Claude cost usually jumps when a rollout adds developers, when Cowork or Office agent sessions send more Opus requests, or when a long-running refactor produces repeated high-cost calls. StackSpend runs anomaly detection against your baseline and flags the surge the same day with the likely driver, so you catch it before the month closes rather than after.
Can I see Claude usage alongside my OpenAI, Cursor, and cloud spend?
Yes. StackSpend puts estimated Claude cost in one view with Anthropic API, OpenAI, Cursor, Hugging Face, Grok, and cloud providers like AWS, GCP, Azure, Snowflake, and Vercel. Instead of reviewing each source separately, you get a single AI-and-cloud total with daily alerts, budgets, and pace-to-forecast across everything you have connected.

Connect Claude. See your spend today.

Read-only setup in under 5 minutes. 90 days of Claude cost history loaded automatically. Daily signals from day one.

Start free trialView setup guide
14-day free trial · No credit card required · Read-only access
Claude Cost Monitoring Tool — StackSpend