Support providing separate API keys for strong and weak models
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.5k
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
Currently the controller only takes a scalar value API key argument. If I want to override the default API key for a specific call both models need to be from the same provider. I'd like to be able to provide a dict of { litellm_provider: key } to the api_key argument to enable precise key control.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the controller's api_key handling and trace how the current scalar key is passed to each model provider. The change is complete when api_key accepts a provider-to-key mapping and each model uses the key for its provider; add or update coverage for separate strong and weak model providers if the existing test structure identifies a location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100