feat: add reasoning_cost to cost breakdown #394
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add reasoning_cost field to billing cost breakdown - Expose reasoning_cost in Usage.Cost module - Include reasoning_cost in telemetry events - Add tests for reasoning token cost calculation Models with token.reasoning pricing (xAI, Azure, Google, etc.) now have their reasoning token costs tracked separately from output_cost. For models without separate reasoning pricing, reasoning_cost is 0. Amp-Thread-ID: https://ampcode.com/threads/T-019c117b-7aa8-72ba-9556-23dc1118034f Co-authored-by: Amp <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #198
Summary
Adds
reasoning_costas a separate field in the cost breakdown, allowing users to see how much they're spending on reasoning tokens.Changes
reasoning_costcalculation viatoken_reasoning_item?/1filter and include it in the returned cost mapreasoning_costin breakdown and merge it into usagereasoning_costin telemetry eventsHow It Works
token.reasoningpricing components (xAI grok-3-mini, Azure, Google Gemini 2.5, OpenRouter models) now have their reasoning token costs tracked separatelyreasoning_costis included inoutput_cost(for backwards compatibility) but also exposed independentlyreasoning_costis 0Testing