Repository navigation
Kaapi: Simplify guardrails routing #143
Description
Is your feature request related to a problem?
There are currently 16 near-identical guardrails routes in the Kaapi backend, creating unnecessary complexity. Every new guardrails API requires a corresponding change in the backend, which is inefficient.
Describe the solution you'd like
- Add a generic catch-all wrapper/utility router in the Kaapi backend to reduce wiring for new guardrails endpoints.
- Explore consolidating the guardrails APIs for improved developer UX.
Original issue
Context
All 16 guardrails routes are mirrored in the Kaapi backend as a proxy layer over kaapi-guardrails (IP whitelisting + org/prod ID header). The 16 come from CRUD fan-out per endpoint. Concern raised: too many near-identical routes; every new guardrails API would need a 1:1 change in the backend.
Direction agreed
- (a) Add a generic catch-all wrapper/utility router in the Kaapi backend so new guardrails endpoints need minimal wiring.
- (b) Explore consolidating the guardrails APIs themselves (e.g., LLM vs non-LLM validator split) for better developer UX.
Activity
[-]Add generic catch-all wrapper router for guardrails proxy layer and propose API consolidation[/-][+]Kaapi: Simplify guardrails routing[/+]Prajna1999 commentedon Aug 21, 2026
duplicate issue ProjectTech4DevAI/kaapi-backend#1151