Skip to content

fix(pricing): add Azure GPT-5.6 cache write rates - #37635

Closed
qdivan wants to merge 1 commit into
BerriAI:litellm_internal_stagingfrom
qdivan:fix/azure-gpt56-cache-write-pricing
Closed

fix(pricing): add Azure GPT-5.6 cache write rates#37635
qdivan wants to merge 1 commit into
BerriAI:litellm_internal_stagingfrom
qdivan:fix/azure-gpt56-cache-write-pricing

Conversation

@qdivan

@qdivan qdivan commented Aug 20, 2026

Copy link
Copy Markdown

TLDR

Problem this solves:

  • Azure GPT-5.6 cache writes are billed at zero

How it solves it:

  • Adds cache-write rates for every Azure GPT-5.6 price entry

User Flow

Before: a platform team sees cached Azure prompt spend missing from proxy logs

  1. They send POST https://litellm-domain/v1/chat/completions to an Azure GPT-5.6 deployment with a cached system prompt
  2. The response returns HTTP 200 with cache_write_tokens in prompt_tokens_details
  3. They open https://litellm-domain/ui/?page=logs and see the cache-write portion recorded at $0

After: the same request records cache writes at Azure's documented 1.25x input rate

  1. They send the same POST https://litellm-domain/v1/chat/completions request to the same Azure GPT-5.6 deployment
  2. The response returns HTTP 200 with the same cache_write_tokens usage details
  3. They open https://litellm-domain/ui/?page=logs and see non-zero cache-write spend

Relevant issues

Fixes #37631

Linear ticket

Pre-Submission checklist

  • I have added meaningful tests
  • The handful of test files covering my change pass locally
  • My PR passes required local formatting checks
  • My PR's scope is as isolated as possible; it only solves 1 specific problem
  • I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review

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)

  • Live Azure proxy verification remains for CI or a credentialed environment

Final Attestation

  • The regression test covers each affected Azure GPT-5.6 pricing entry

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@codecov

codecov Bot commented Aug 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@codspeed-hq

codspeed-hq Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 31 untouched benchmarks


Comparing qdivan:fix/azure-gpt56-cache-write-pricing (cadef9f) with litellm_internal_staging (6d47468)

Open in CodSpeed

@qdivan

qdivan commented Aug 20, 2026

Copy link
Copy Markdown
Author

I’m closing this draft because #35125 already covers the same 12 Azure GPT-5.6 global/US/EU cache-write pricing entries and regression coverage; #35841 also overlaps the global Terra/Luna portion. Withdrawing this duplicate to avoid splitting maintainer review.

@qdivan qdivan closed this Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: azure/gpt-5.6* entries missing cache_creation_input_token_cost — cache writes billed at zero since v1.97.0

2 participants