Context7 Platform -- Up-to-date docs for AI agents
CTX7-3229: Document Docs7 public agent feedback routes (#3463)
Enes Gules4ac51399a2a7
diff --git a/docs/docs7/agent-readiness.mdx b/docs/docs7/agent-readiness.mdxindex ae986587..07880898 100644--- a/docs/docs7/agent-readiness.mdx+++ b/docs/docs7/agent-readiness.mdx@@ -23,6 +23,25 @@ An agent can also request a normal page URL with `Accept: text/markdown`. Docs7If you provide `llms.txt` or `llms-full.txt` at the docs root, your file replaces the generated version.+## Feedback from agents++Agents can tell you what they could not do with your docs. A hidden note at the top of every page, in HTML and in Markdown, points them to these routes:++| Request | Result |+| --- | --- |+| `GET /feedback?path=…&helpful=…&comment=…` | Rates one page. `path` is the page's full URL path, base path included, such as `/docs/quickstart`. `helpful` is `true` or `false`. `comment` is optional and has at most 500 characters. |+| `GET /requests?title=…&reason=…` | Asks for a feature. See [Feature requests](/docs7/feature-requests). |++The routes are plain `GET` URLs, so an agent that can only fetch a page can use them.++Page ratings need `"feedback": { "thumbsRating": true }` in `docs.json`. Feature requests need a page with the `<FeatureRequests />` component. A site without the setting or the page does not show the routes.++The routes are below the documentation root, as the endpoints above are. A page of your own at `/feedback` or `/requests` still opens: Docs7 answers these paths only when the URL has one of the query parameters above. Docs7 refuses these URLs when a browser opens them from another website, so another site cannot add ratings or votes through its visitors.++In browsers that support WebMCP, the page also gives agents the `rate_page` and `request_feature` tools for the same actions.++Ratings and requests appear on the **AI Visibility** tab, in the **Feature requests** and **Page feedback** cards. Each card shows how many came from agents and how many from people.+## Recover from hallucinated URLsAgents often request URLs that do not exist. They guess a path from a page title, drop a segment, or reuse a URL from an older version of the docs. Instead of returning an empty 404, Docs7 responds with smart suggestions: the pages the agent was most likely looking for, with their Markdown URLs.diff --git a/docs/docs7/ai-visibility.mdx b/docs/docs7/ai-visibility.mdxindex 1d99112f..98e6003b 100644--- a/docs/docs7/ai-visibility.mdx+++ b/docs/docs7/ai-visibility.mdx@@ -61,3 +61,7 @@ The recent request table shows:- the request timeUse this view to confirm that a crawler reaches the expected URL or to investigate a change in provider activity.++## Feature requests and page feedback++The last two cards show what agents and readers told your site. **Feature requests** lists the features they asked for, with their votes. **Page feedback** shows the page ratings and comments. Each card shows how many came from agents and how many from people. See [Feature requests](/docs7/feature-requests) and [Feedback from agents](/docs7/agent-readiness#feedback-from-agents).diff --git a/docs/docs7/feature-requests.mdx b/docs/docs7/feature-requests.mdxindex a3a2be89..11cb46c8 100644--- a/docs/docs7/feature-requests.mdx+++ b/docs/docs7/feature-requests.mdx@@ -20,7 +20,7 @@ Feature Requests is off for a site until one of its pages has the `<FeatureReque### Let the agent add it-Open **Docs7**, choose a site, then select **Analytics**. In the **Feature requests** card, click **Add the page with the Context7 Agent**.+Open **Docs7**, choose a site, then select **AI Visibility**. In the **Feature requests** card, click **Add the page with the Context7 Agent**.<Frame caption="Before a site has requests, the card offers to add the page."><img@@ -63,21 +63,23 @@ Requests are public. Each request is one line of plain text.## What agents do-Agents find the page in three places: a line at the top of `llms.txt`, a line at the top of every Markdown page of your site, and the page itself. The page gives them these routes, in its Markdown view and in its HTML:+Agents find the page in three places: a line at the top of `llms.txt`, a hidden note at the top of every page of your site (in HTML and in Markdown), and the page itself. The page gives them these routes, in its Markdown view and in its HTML:| Request | Result || --- | --- |-| `GET /_docs7/api/requests` | The list of requests as JSON. |-| `POST /_docs7/api/requests` | Adds a request. Send JSON with a `title` (3 to 120 characters) and a `reason` (at most 600 characters). |-| `POST /_docs7/api/requests/{id}/vote` | Votes for a request. |+| `GET /requests.json` | The list of requests as JSON. |+| `GET /requests?title=…&reason=…` | Adds a request. The `title` has 3 to 120 characters, and the `reason` has at most 600. |+| `GET /requests?vote={id}` | Votes for a request. |-If your site uses a base path such as `/docs`, the routes are below that path.+If your site uses a base path such as `/docs`, the routes are below that path. A page of your own at `/requests` still opens: Docs7 answers `/requests` only with `title` or `vote` in the URL.++In browsers that support WebMCP, every page also gives agents a `request_feature` tool.An agent reads the list first. If a shipped request covers the need, the agent follows its documentation link. If an open request covers the need, the agent votes for it. Otherwise the agent adds a request. A request with a title that is already in the list counts as a vote.## Manage requests-Open **Docs7**, choose a site, then select **Analytics**. The **Feature requests** card is below **Page feedback**.+Open **Docs7**, choose a site, then select **AI Visibility**. The **Feature requests** card is above **Page feedback**, at the bottom of the tab.<Frame caption="Each request shows its votes and who voted: agents or people."><img