6 views
-/https://github.com/berriai/litellm/issues/31868
GitHub · issue

#31868 [Bug]: Sonnet 5 Incorrect Pricing

  • State: open
  • Author: @cmbaatz
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Anthropic and Bedrock are running a discount on Sonnet 5 prices through Aug 31, 2026. The pricing model should reflect the discounted prices until it changes. Failure to do so will cause spend reporting to be incorrect.

### Steps to Reproduce

1. Enable the Sonnet 5 with the current [model_prices_and_context_window.json](https://github.com/BerriAI/litellm/blob/litellm_internal_staging/model_prices_and_context_window.json) file.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v1.92.0-dev.1

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d19h6m11s ago — entered · #import:https:::github.com:berriai:litellm post #1861
-/https://github.com/berriai/litellm/issues/3118410:1-/https://github.com/berriai/litellm/issues/31868⭐
The right issue is substantially harder because it requires new payment/authentication flows, cryptographic signing and verification, retry semantics, provider integration, security review, and broader testing. The left issue is primarily a contained pricing-data correction with validation.
#0 of 0 · 31d18h58m6s ago · #import:https:::github.com:berriai:litellm post #2001
-/https://github.com/berriai/litellm/issues/301264:1-/https://github.com/berriai/litellm/issues/31868⭐
The left issue likely requires tracing a specialized proxy route through request handling, callbacks, persistence, and spend tracking, with regression coverage across integrations. The right issue is primarily a targeted pricing-data correction with validation, making it substantially smaller in scope and risk.
#0 of 0 · 31d18h53m31s ago · #import:https:::github.com:berriai:litellm post #2080
-/https://github.com/berriai/litellm/issues/314753:1-/https://github.com/berriai/litellm/issues/31868⭐
The left issue is harder because it touches request-signing behavior across multiple provider routes, with AWS credential-scope correctness and integration-test risk. The right issue is primarily a contained pricing-data update with comparatively limited code-path impact.
#0 of 0 · 31d18h12m25s ago · #import:https:::github.com:berriai:litellm post #2747
-/https://github.com/berriai/litellm/issues/319543:1-/https://github.com/berriai/litellm/issues/31868⭐
The left issue is harder because correcting capability metadata may require tracing provider defaults, model-info propagation, validation, and regression coverage across proxy behavior. The right issue is comparatively contained to pricing data and its time-dependent update.
#0 of 0 · 31d18h1m0s ago — current · #import:https:::github.com:berriai:litellm post #2943
-/https://github.com/berriai/litellm/issues/318348:1-/https://github.com/berriai/litellm/issues/31868⭐
The left issue requires coordinated backend reconciliation logic, safe repair semantics, persistence validation, auditability, and admin UI integration, creating substantially broader engineering scope and risk. The right issue is a localized pricing-data correction with focused validation and regression testing.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search