You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the above use case, how we are thinking about using the api_keys from the array?
Random: This could use the one just has been rate limited
How we are thinking about solving it? Or we will leave as it is because we retry anyway and random will pick the another key eventually?
@krrishdholakia I am interested on working on it, can you assign it to me.
My understanding of the problem so that i can have a proper fix:
{
"model_name": "....",
"litellm_params": {
"model": "....",
"api_key": <your-api-key>, # this can be either array or string, if array a random value will be chosen
}
}
Changing the api_key's dataType fromstr to list[str] might have long lasting implications. It is not usually good idea to support like this (based on my experience).
I think if user catch and handle RateLimitError, this can be done without affecting the litellm codebase.
This is just me suggesting, i am still learning and trying litellm, so my answer might not make sense, guidance is appreciated.
The Feature
support passing in api keys as an array to the router
Motivation, pitch
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: