Why it matters
A billing export shows the total, not the developer, model or retry that produced it. CUR 2.0 can now attribute Bedrock spend to the IAM principal behind each individual call, and Claude Code ships OpenTelemetry support to cover the client side.
Tokenmaxxing read
AWS puts the savings at 30-50%, and it comes from ordinary routing discipline: Sonnet 4.5 at $3/$15 per million tokens against Haiku 4.5 at $1/$5 is roughly 67% off routine work, with cached input up to 90% cheaper. Telemetry just shows which tasks sit on the wrong model.
Source takeaway
Instrument the client, not Bedrock — that is where per-session cost and cache-hit ratios live. Coverage is uneven: Claude Code is the worked example, while Cursor shops are held to the first two layers plus that vendor's own admin dashboard.
