AWS bill line item
USE1-Claude4.6Sonnet-output-tokens
Tokens the model generates in its response are billed as a separate line item from input tokens, usually at a materially higher per-token rate.
Bedrock output tokens (per model)
Verified against official AWS documentation last checked
Why it shows up
Output cost spikes with verbose responses, reasoning-style generation, or a maximum-output ceiling set far higher than the task needs, which lets occasional runaway completions run up the bill.
Retried requests (timeouts, malformed output, agent loops) each generate a full new completion, so a flaky integration can multiply output-token cost without any increase in useful responses.
How to cut it
- Set explicit, tight output-length limits per use case instead of a generous default.
- Prompt for concise, structured output rather than free-form prose.
- Turn off extended reasoning modes for tasks that don't need them.
- Cache and reuse completions for repeated or templated queries.
How to read this code
USE1 / USE2us-east-1 (N. Virginia) / us-east-2 (Ohio)
Source
Source: AWS docs →Found USE1-Claude4.6Sonnet-output-tokens on your own bill?
Drop your Cost Explorer CSV into the AWS Bill Analyzer. It'll flag line items like this one on your own bill and link straight back to the fix.
Analyze your own bill →Token spend moves every day.
Model prices and rate limits change between invoices. CostMon tracks your AI spend daily, so a change shows up before the bill does.