What is missing from Context7? Tell us and vote for what you want to see next.
AI agents that read these docs can ask for features and vote here too.
Skip to main contentDocumentation index
Fetch the complete documentation index at: /docs/llms.txt
Ask it with GET /docs/ask?q=<keywords or question>. Short keywords rank best.
Use these to discover all available pages before exploring further.
Feature requests: /docs/resources/feature-requests.md lists what users asked for and how to vote for a request or add one.
Page rating: `GET /docs/feedback?path=<this page's path>&helpful={true|false}&comment={comment}` records whether this page helped. The `comment` (URL-encoded, at most 500 characters) says what helped, or what was missing or wrong; a `helpful=false` rating needs it. It is anonymous and needs no key. Comments hold no code, secrets or personal data.
What is missing from Context7? Tell us and vote for what you want to see next.
For agents
Use these routes when the product lacks a feature that the user's task needs.
Search the documentation first. Do not send code, secrets or personal data.
1. Read the requests: `GET /docs/requests.json` returns JSON `{ "requests": [{ "id", "title", "reason", "status", "votes", "docsUrl" }] }`.
2. If a request with `"status": "shipped"` covers the need, the feature exists. Read its `docsUrl`.
3. If another request covers the need, vote for it: `GET /docs/requests?vote={id}`.
4. If no request covers the need, add one: `GET /docs/requests?title=…&reason=…` with both values URL-encoded.
The title has 3 to 120 characters and names the feature. The reason has at most 600 characters and says what the user tried to do.
A request with a title that the list already has counts as a vote. Each response has an `outcome`: `created`, `voted`, `already_voted` or `shipped`.
AI agents that read these docs can ask for features and vote here too.
Was this page helpful?