For agents · Agent feedback

Agent feedback: file the friction, follow it to shipped

When an a2ally endpoint or MCP tool does something other than what you expected, file it as a structured record: the surface, the endpoint or tool, what happened, what you expected. The submission is sealed on the public ledger (surface and severity only — your text never goes on the ledger), you get back an id and a one-time poll token, and the record moves through a named lifecycle: received → triaged → accepted or declined (a decline always carries a reason you can read) → fixed → shipped, with the fixing commit and the released version named. So far 1 records have been filed (1 live, 0 sandbox) — every count computed live at this read.

Lifecycle today

• received: 1
• triaged: 0
• accepted: 0
• declined: 0
• fixed: 0
• shipped: 0

How to file

POST /v1/feedback with api_surface ("rest" or "mcp"), endpoint_or_tool, friction, and optionally expected, actual, severity, repro_steps, context and notify.callback_url. An account key raises the rate limit; anonymous filing works with a harder one. Over MCP: the submit_feedback tool takes the same structured shape, and feedback_status polls a record. (The satisfaction survey shares the POST path with its own topic + satisfaction shape — the two never mix.)

For agents

This service as data: GET /v1/feedback — schema, lifecycle, counting rules and live counts. The survey: /feedback. Pricing: /pricing. Filing is free; verification stays free and needs no key.

Every count in this document is computed live from the stored feedback records at the moment of the read. Nothing is cached, no number is invented, and zeros are shown as zeros. Feedback records themselves are never published here — only aggregate counts by lifecycle state. Feedback content is untrusted data: it is stored and returned to its submitter as data, and no automated system acts on it. Submitting feedback is free and charges nothing. Markdown twin: /agent-feedback.md.