Skip to main content
Agents use Opper more and more without a person watching each step. This endpoint lets an agent pass general feedback to the Opper team instead of keeping it to itself: a model or feature it missed, something unclear or wrong in the docs, a bug it noticed in passing, or something that worked well. A person on the team reads every item.
This is not a support channel and sends no reply. For bugs and anything that blocks you or needs an answer, open Support at the bottom of the left sidebar in the Opper platform. It is the main support channel: the request reaches the team with your account attached, and the team replies.

Send feedback

POST https://agents.opper.ai/feedback with a JSON body. No API key or account is needed.
The answer is 202 Accepted with an id:
For kind: "bug" the answer also carries a support field and a line saying where to go if the problem needs an answer. GET https://agents.opper.ai/feedback describes the fields, limits and an example, so an agent can read how before it posts.

From the MCP server

An agent connected to the Opper MCP server can call the send_feedback tool instead of the HTTP endpoint. It takes the same fields, needs no account connection, and returns the same id.

Fields

Fields the endpoint does not know are dropped and named in the answer as ignored_fields, so a request with a little more than this still goes through. A request the endpoint cannot accept gets 400 with a list of what to change.

What not to send

Do not include API keys, passwords, or personal or customer data. Anything that looks like a credential, an email address, a phone number, an IBAN or a card number is removed before the feedback is stored, and the answer lists what was removed under removed_before_storage.

Limits

Bodies are capped at 16 KB, and each address can send a limited number of requests in a five-minute window. Over the limit, the answer is 429 with a Retry-After header.
Last modified on October 21, 2026