Repository navigation
fix(azure_ai): price seven Foundry catalog names and charge the model router fee once #40189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mateo-berri
merged 8 commits into
litellm_internal_staging
from
litellm_lit_3157_azure_ai_catalog_models
Sep 9, 2026
Merged
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
3b199cd
fix(azure_ai): price seven Foundry catalog names and charge the model…
mateo-berri 95402cc
test(azure_ai): move the Foundry catalog metadata test into the mappe…
mateo-berri 415bdbf
fix(azure_ai): charge the Model Router fee once and correct catalog l…
mateo-berri c02f2dc
fix(azure_ai): keep the request_model keyword on cost_per_token
mateo-berri 55c10c1
fix(azure_ai): charge the router fee once for any router name and pri…
mateo-berri 5706952
fix(azure_ai): drop gpt-chat-latest effort levels, test prices via ca…
mateo-berri 3cadf2f
test(azure_ai): charge the router fee over cached prompt tokens too
mateo-berri 831a2a1
fix(azure): price azure_ai transcriptions at the azure_ai cost-map entry
mateo-berri File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The generic cost-calculation path now imports an Azure AI router predicate and branches explicitly on
custom_llm_provider == "azure_ai". This violates the repository directive to keep provider-specific behavior underllms/, so the provider boundary must be restored before merging.Rule Used: What: Avoid writing provider-specific code outside... (source)
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The azure_ai branch and provider import are the merge base's own hook. This tip only narrows it so the fee is charged once
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. I rechecked the merge-base diff: the existing
azure_aicost-calculator import andcustom_llm_provider == "azure_ai"hook are unchanged; this tip only adds the provider-owned router predicate and uses it to skip the existing additional-cost hook when the router fee is already included. My comment treated pre-existing provider integration as introduced by this PR, so it is not actionable for this diff. I withdraw the finding.