-
Notifications
You must be signed in to change notification settings - Fork 747
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
Estimate token usage + dry run option #318
Comments
Thanks for the thoughtful feature request, the function-calling example is a compelling one. We'll think about this. Can you share an example of how you'd want to code the logic to proceed or not proceed based on the token count? |
I use function calling extensively. I'd love a simple function that returned a token count given completion input, e.g. I want to ensure that I respect rate limits before I ever hit them. Rate limiting libraries such as Bottleneck can be configured to respect both the request and token limits, but I need the token counts before I make the request |
I don't expect to get to this anytime soon, but I would be interested in PR's implementing this that add the functionality to the |
If anyone is stuck at this problem...
|
Confirm this is a feature request for the Node library and not the underlying OpenAI API.
Describe the feature or improvement you're requesting
There a couple nodejs tokenizers laying around npm land:
However, they have to be kept maintained and up to date with the official tiktoken. It feels very natural that such a tool be apart of this repository and updated regularly by the openai team. I feel that pre-request token estimation is vital to ensuring hobbyist developers don't unknowingly succumb to financial demise.
Why apart of this library?
Take function calling for example:
I could intercept this function call above to view what data is sent to chatGPT so I can figure out how many tokens this call takes with the
message
+ thefunctions
, pipe them into gpt-tokenizer and see how many tokens are used. But if it were to be built into the API itself then you can have a dry run option on your nodejs api functions that estimate cost and then the developer could determine in the logic if they want to proceed with the actual run.What else could be very helpful would be to include some parameter whether in the configuration or when calling api functions such that if the tokens and/or usd cost exceeds a certain limit the call auto fails and doesn't actually get executed.
Additional context
No response
The text was updated successfully, but these errors were encountered: