POST /v1/web/feedback records whether a result was accurate. A rating of bad puts the request in front of the team with what you saw, so a page we read wrong gets looked at and fixed. Ratings are free, and rating the same request again replaces the earlier rating.
When to use it
- A scrape left out part of the page, such as a price table or a list of job openings.
- A result came back as a blocked or error page, or as content from the wrong page.
- An agent noticed the content it received does not answer what it asked.
Which request you are rating
Every response carries anX-Request-Id header, and the SDKs keep the latest one for you. Send that id as requestId. If you no longer have it, send the url instead and we rate your most recent request for that URL in the last 24 hours. Requests can be rated for 30 days.
Example request
Example response
Fields
string
The request to rate, from its
X-Request-Id header. Give this or url.string
The URL that was read. Rates your most recent request for it in the last 24 hours. Give this or
requestId.string
required
good or bad.string[]
What was wrong, for a
bad rating: missing_content, wrong_content, blocked, slow, formatting or other.string
What you expected to see, in your own words. Up to 500 characters.
Response fields
string
The rating’s id.
string
The request that was rated.
string
The rating you gave.
From an agent
The MCP server has a freefeedback tool with the same fields. Every tool result includes usage.requestId, so an agent can rate the call it just made.