Problem: While we currently support OpenAI and Google Gemini APIs, user requests indicate a need for integration with additional third-party providers like Groq and Cerebras.
Proposed Solution: Adding a dedicated API key field will enable users to leverage these external services.
Alternatives Considered: A more comprehensive solution would allow administrators to customize the number and type of API keys per user. However, this approach requires significant development effort. To prioritize a solution with minimal impact, we're focusing on adding a single third-party API key field, which will address a majority of user needs.
Implementation Steps:
[x] Integrate third-party API key support into the multi-chat functionality.
[x] Introduce a flag to the OpenAI Executor allowing for a switch to the third-party API provider
Problem: While we currently support OpenAI and Google Gemini APIs, user requests indicate a need for integration with additional third-party providers like Groq and Cerebras.
Proposed Solution: Adding a dedicated API key field will enable users to leverage these external services.
Alternatives Considered: A more comprehensive solution would allow administrators to customize the number and type of API keys per user. However, this approach requires significant development effort. To prioritize a solution with minimal impact, we're focusing on adding a single third-party API key field, which will address a majority of user needs.
Implementation Steps: