Update perplexity cost tracking #15743
Open
+526
−34
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.
Title
Add Perplexity cost extraction from API response
Relevant issues
Fixes #15547
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-unit
Type
Bug FIx
Changes
This PR adds cost extraction functionality to Perplexity's chat transformation, allowing Perplexity to override LiteLLM's cost calculation by providing its own cost information in the API response.
I have updated perplexity provider to base_llm_http_handler and its own transformation methods. And I have used concept of over riding the cost as now perplexity provides cost in its response itself
This change ensures Perplexity users get accurate cost tracking that reflects the provider's actual pricing, improving cost transparency and accuracy for Perplexity API usage.
Change in perplexity API repsonse: