fix(gemini): include IMAGE tokens in input cost calculation #18153
+55
−2
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.
Relevant issues
Fixes #14285
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🐛 Bug Fix
Changes
When sending images as input to Gemini, LiteLLM was not counting IMAGE tokens for cost calculation. The API returns
promptTokensDetailswith separate modalities:{ "promptTokenCount": 262, "promptTokensDetails": [ {"modality": "TEXT", "tokenCount": 4}, {"modality": "IMAGE", "tokenCount": 258} ] }LiteLLM only counted TEXT tokens (4), ignoring IMAGE tokens (258), resulting in ~98% undercharged costs for image inputs.
Example
Solution
According to Google's Gemini API pricing, image input tokens are priced the same as text tokens for all Gemini models:
The fix adds IMAGE tokens to
text_tokensin_calculate_usage():Tests Added
test_vertex_ai_usage_metadata_with_image_input_tokens- IMAGE tokens in promptTokensDetailstest_vertex_ai_usage_metadata_with_image_input_tokens_reverse_order- Order independence