Repository navigation
Unified API: Kaapi Backend as a Proxy #861
Description
Is your feature request related to a problem?
Kaapi users cannot utilize LLM_CALL standalone components without going through the backend. This limitation hinders their ability to efficiently use features like guardrails and configuration.
Describe the solution you'd like
- Extend the current LLM_CALL endpoint.
- Enable the Kaapi backend to serve as a proxy server for clients.
Original issue
Currently if Kaapi users want to not make calls via backend but want to make use of LLM_CALL standalone components i.e guardrails, config etc, there is no way to do that. Explore how the current LLM_CALL endpoint be extended to enable Kaapi backend to be a de-facto proxy server for our clients.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Unified API: Kaapi backend as proxy[/-][+]LLM_CALL: Enhance standalone access[/+][-]LLM_CALL: Enhance standalone access[/-][+]Unified API: Kaapi Backend as a Proxy[/+]