Claude coding spend is hard to pin down

What goes wrong

Claude shows up through editors, agents, and other clients that all talk to Anthropic in different ways. Provider consoles and editor usage screens each tell part of the story. None of them reliably answer “which coding traffic burned this week's Claude spend?” while you can still do something about it.

Why it matters

Claude prices and large contexts make spend swing fast. Without a model-level picture and a sense of chat vs agents vs everything else, teams either under-buy plan allowance or overreact to one noisy week. Finance sees a line item; engineering cannot map it to behavior.

What good looks like

Observed requests labeled by provider and model, with rough usage feeding a this-month cost view you can check against your plan balance — clearly estimates, not the invoice.

How Aura Wire helps

Aura Wire watches the Anthropic (and other) traffic from tools you route through it, then turns those observations into cost views with per-model prices you set locally.

• Provider and model breakdowns in live traffic and cost views
• This-month projection and a place to snapshot your plan balance
• Sanitized records only — prompts and answers are not stored