Proposal: Add Feedback as a Standard Resource on the Langgraph API Server

OSS Product Help LangGraph
, ,
1

Hello,

I’d like to bring a proposal forward that would create a /feedback route and accompanying Resource definitions to the Langgraph API Server.

There exists a pre-signed url flow for something like this today, however in enterprise environments, rarely would the feedback-giving application have network or auth access to a self-hosted or BYOC Langsmith instance. This proposal would eliminate the need for any access to Langsmith from a feedback-giving application, and instead delegate that work to the same agent that produced the response that needs feedback. The sensible defaults could/would still be api.langsmith.com, the SaaS endpoint.

POST /threads/{thread_id}/runs/{run_id}/feedback and POST /runs/{run_id}/feedback for stateless runs, plus GET on the same paths. LangSmith feedback schema (key, score, value, comment, correction, metadata) would map to the same as create_feedback.

Return 202 and write asynchronously. Add feedback as a resource in the auth handler.

I am working on doing this in a custom route for now for our enterprise, but I figure it would be good to get community/maintainer discussion on it.

2

Hi @paychex-ssmithrand, I brought this up to our LangSmith Deployment team to see if this is something they’d be interested to add to the agent server. For now though, adding a custom route seems like a good approach.