fix: added custom token pricing #143
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.
PR Description
This pull request aims to address the issue of custom token pricing by introducing changes to the configuration and provider files.
Changes Made
config.jsonfile, the language model'smodelattribute has been replaced with a nested object containingname,input_token_cost, andoutput_token_costproperties.provider.pyfile, default input and output token costs have been added to theLLMProviderclass, and thechat_completionmethod has been updated to utilize the new token cost values.These modifications enable the customization of token pricing for the language model, providing more flexibility and control over the cost associated with input and output tokens.
Original Description
None