For AI agents: the complete documentation index for the Restless API is available at https://build.restless.ai/llms.txt. This page is also available as Markdown at https://build.restless.ai/usecases/turn-agent-feedback-into-a-docs-fix.md (or send an Accept: text/markdown request header).

Turn agent feedback into a docs fix

Read what confused a machine consumer of the API, fix the docs, then close the note out.

Agents reading an API leave notes when something confuses or blocks them. Those notes are the most direct signal you get about where the documentation is wrong, and they pile up unless someone works the queue.

This reads the open notes, sorts them into corrections to existing copy and knowledge that was never written down, applies each one, and archives what has been handled so the queue keeps reflecting real remaining work.

A curated task for the Restless API: the calls to make, in order, as the API's owner wrote them. Humans run this as a guided conversation at the same URL; the steps below are that same recipe.

Steps

1. Confirm the identity and access behind the API key with `GET /api/v1/me`.
2. Pick the target project. If you only have an example slug, verify it with `GET /api/v1/projects/{slug}`, or browse options via `GET /api/v1/projects`.
3. Read the open notes with `GET /api/v1/projects/{slug}/feedback`, passing `status=active`. These are captured by the docs MCP server's `send_feedback` tool, newest first.
4. Sort them. A note about documentation that is missing or wrong is a content fix. A note about knowledge the docs never covered is a new context item.
5. For a content fix, read the current copy with `GET /api/v1/projects/{slug}/content` and apply the correction with `PATCH /api/v1/projects/{slug}/content`.
6. For missing knowledge, add it with `POST /api/v1/projects/{slug}/context`.
7. Close each note you acted on with `PATCH /api/v1/projects/{slug}/feedback/{feedbackId}`, setting `status` to `archived`. Leave anything you did not act on active.