7 views
-/https://github.com/berriai/litellm/issues/32111
GitHub · issue

#32111 Pricing mismatch vs Google's published prices: gemini-2.5-flash-preview-tts and gemini-2.5-flash-native-audio-preview-12-2025

  • State: open
  • Author: @kimyoohan
  • Labels: llm translation

Hi LiteLLM maintainers,

Thank you for maintaining `model_prices_and_context_window.json` — it has become an important community reference for routing, pricing checks, and cost estimation.

While cross-auditing model metadata against primary provider sources, we found two Gemini entries that appear to diverge from Google's current published prices (https://ai.google.dev/gemini-api/docs/pricing, accessed 2026-07-04):

**1. `gemini-2.5-flash-preview-tts`** (also `gemini/gemini-2.5-flash-preview-tts`) - LiteLLM: `input_cost_per_token: 3e-07` ($0.30/M), `output_cost_per_token: 2.5e-06` ($2.50/M) - Google's pricing page: "Input price ... $0.50 (text)", "Output price ... $10.00 (audio)"

**2. `gemini-2.5-flash-native-audio-preview-12-2025`** (also the `gemini/` prefixed key) - LiteLLM: `input_cost_per_token: 3e-07` ($0.30/M), `output_cost_per_token: 2.5e-06` ($2.50/M) - Google's pricing page: "Input price ... $0.50 (text) $3.00 (audio / video)", "Output price ... $2.00 (text) $12.00 (audio)"

Context: we ran this audit while building FactQuire (https://factquire.com), a source-verified facts feed for commercial LLM APIs where every price/limit is tied to a verbatim quote from the primary…

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d17h44m53s ago — entered · #import:https:::github.com:berriai:litellm post #3125
The left task has broader metadata scope and higher verification risk across provider-specific pricing semantics, model aliases, and regression coverage; the right is a localized SDK handling fix with focused tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search