feat(ai): Options for custom model cost mappings #94858
Merged
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.
Since this is still a very young field, there is a lot of irregularities in model naming. This PR introduces an option to configure custom model mappings, where we can assign alternative names to existing models in our pricing map. Often the same models have different names, depending on where they are hosted.
For example:

We need to have a way to add custom mappings, which can be easily changed and quickly deployed - that's why the options are used.