Skip to content

Guardrails: Expose dedicated endpoint #935

Closed
Feature
#939
Closed
Guardrails: Expose dedicated endpoint#935
Feature
#939
Assignees
Prajna1999
Labels
enhancementNew feature or requestreleased on @main

Description

@Prajna1999
Prajna1999
opened on Jun 15, 2026

Is your feature request related to a problem?
We currently do not have a dedicated endpoint for using guardrails directly, which can complicate the integration process and delay development.

Describe the solution you'd like

  • Expose an endpoint that allows users to access only guardrails.
  • Ensure that this endpoint does not route through the LLM/call endpoint.
Original issue

TBD.

Requirements will be added when things are clear

Activity

  1. Prajna1999
    self-assigned this
    on Jun 15, 2026
  2. Prajna1999
    added the
    Feature
    issue type on Jun 15, 2026
  3. Prajna1999
    added this to Kaapi-devon Jun 15, 2026
  4. github-project-automation
    moved this to To Do in Kaapi-devon Jun 15, 2026
  5. github-actions
    changed the title [-]Guardrails as a Service: Expose and endpoint to use only guardrails instead of routing through llm/call endpoint[/-] [+]Guardrails: Expose dedicated endpoint[/+] on Jun 15, 2026
  6. Prajna1999
    added
    enhancementNew feature or request
    on Jun 15, 2026
  7. Prajna1999
    moved this from To Do to In Progress in Kaapi-devon Jun 15, 2026
  8. Prajna1999
    linked a pull request that will close this issueGuardrails: Expose Dedicated Endpoint #939on Jun 23, 2026
  9. Prajna1999
    moved this from In Progress to In Review in Kaapi-devon Jun 29, 2026
  10. Prajna1999
    closed this as completedin #939on Jun 29, 2026
  11. github-project-automation
    moved this from In Review to Closed in Kaapi-devon Jun 29, 2026

  12. github-actions commented on Jul 1, 2026

    @github-actions
    github-actionsBot
    on Jul 1, 2026 – with GitHub Actions

    🎉 This issue has been resolved in version 1.3.0-main.1 🎉

    The release is available on GitHub release

    Your semantic-release bot 📦🚀

  13. github-actions
    added
    released on @main
    on Jul 1, 2026

  14. github-actions commented on Jul 1, 2026

    @github-actions
    github-actionsBot
    on Jul 1, 2026 – with GitHub Actions

    🎉 This issue has been resolved in version 1.2.2-main.1 🎉

    The release is available on GitHub release

    Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestreleased on @main

Type

Feature

Projects

  • Kaapi-dev
    Status
    Closed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions