fix(pricing): add Azure GPT-5.6 cache write rates - #37635
Closed
qdivan wants to merge 1 commit into
Closed
Conversation
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
Author
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
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.
TLDR
Problem this solves:
How it solves it:
User Flow
Before: a platform team sees cached Azure prompt spend missing from proxy logs
cache_write_tokensinprompt_tokens_detailsAfter: the same request records cache writes at Azure's documented 1.25x input rate
cache_write_tokensusage detailsRelevant issues
Fixes #37631
Linear ticket
Pre-Submission checklist
Screenshots / Proof of Fix
A live Azure deployment is required for end-to-end proxy proof and was not available in this environment. The focused regression test validates all global, US, and EU Azure GPT-5.6 entries with cache-write token usage against their documented cache-write rates.
Type
🐛 Bug Fix
Caveats (if any)
Final Attestation