Best practice for remote APIs that require a proxy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.5k
- Forks
- 998
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 10
Description
In some corporate environment, there is no direct access to remote API.
One option is provide support for proxies (see https://github.com/simonw/llm/issues/518), e.g. by having llm let specify an alternate endpoint. When adding a new model via a plugin, this would mean asking for the api key AND an optional endpoint.
Another option is to create a new plugin for each model (or family of models) that requires a proxy access, and the Python code of the plugin would point to the proxy instead of the default endpoint.
@simonw
Any recommendation about the best way to proceed?
Contributor guide
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 by reviewing issue #518 and the two approaches described here: configurable alternate endpoints or separate plugins that target proxies. The issue is asking for a maintainer recommendation, so the desired implementation and completion criteria are not yet defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100