Repository navigation
[FEATURE]: Support for multiple API vendors #51794
Description
Activity
This issue might be a duplicate of existing issues. Please check:
- [FEATURE]: Interactive custom provider registration flow in /connect command palette #49091: Proposes an interactive
/connectflow for adding third-party providers with an endpoint URL and API key. - [FEATURE]: Add a textbox to set OpenAI compatible URL for local or remote custom connectors #44450: Requests a base URL field for OpenAI-compatible custom providers in
/connect.
- [FEATURE]: Interactive custom provider registration flow in /connect command palette #49091: Proposes an interactive
This issue might be a duplicate of existing issues. Please check:
- [FEATURE]: Interactive custom provider registration flow in /connect command palette #49091: Proposes an interactive
/connectflow for adding third-party providers with an endpoint URL and API key. - [FEATURE]: Add a textbox to set OpenAI compatible URL for local or remote custom connectors #44450: Requests a base URL field for OpenAI-compatible custom providers in
/connect.
no, it's not, even if it's similiar. I wrote explictly of permitting API keys from other vendors, instead using only one, who may be expensive
- [FEATURE]: Interactive custom provider registration flow in /connect command palette #49091: Proposes an interactive
Metadata
Metadata
Assignees
Labels
No labels
Feature hasn't been suggested before.
Describe the enhancement you want to request
Please modify the requirments, so it would allow to use API keys from different vendors and not only Antropic.
Requiring to use API that require any kind of payments makes thia agent useless for those who can't afford themself to pay for the API key