NVIDIA-NeMo / NVIDIA-NeMo/Guardrails

feature: Native support for v1/responses endpoint

Open
#2,273 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement status: needs triage
Dominant language
Python
Stars
7.2k
Forks
842
Avg merge
3d 1h
Merged PRs (30d)
25

Description

Did you check the docs?
  • I have read all the NeMo-Guardrails docs
Is your feature request related to a problem? Please describe.

OpenAI's v1/responses endpoint is the de-facto API for agentic tool-use, superseding v1/chat/completions. While OpenAI still supports the Chat Completions API, the Responses API is far more performant agentic use cases. Furthermore, OpenAI recommends new projects to use Responses over Chat Completions.

Currently, there is no native support for v1/responses payloads in NeMoGuardrails. Developers who rely on the Responses API for their applications would have to write custom code to translate v1/responses payloads to v1/chat/completions in order to use NeMoGuardrails.

Describe the solution you'd like
  • A native /v1/responses client, mirroring the existing /v1/chat/completions client
  • A /v1/responses endpoint in the NeMo Guardrails server, for guardrailed inference proxying
  • A /v1/responses/checks endpoint, for standalone guardrailing
Describe alternatives you've considered

n/a

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing /v1/chat/completions client and server endpoint, then trace how their payloads and standalone checks are handled. Done means native /v1/responses and /v1/responses/checks support is available alongside the existing client and endpoint behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.