# Self-updating docs > Restless reads resolved support conversations, pulls out the part that applies to everyone, and drops it in an inbox to review. Approve it and it becomes context the next person finds on their own. Source: https://www.restless.ai/self-updating-docs Answer a support question once and it usually stays buried in one thread. Restless reads resolved conversations, pulls out the part that applies to everyone, and drops it in an inbox to review. Approve it and it becomes context the next person finds on their own. ## Features - A fix worked out in support gets written down once, so it stops coming back. - Only generic API knowledge is kept, like endpoints, limits, and error meanings. Account details stay in the thread. - Nothing publishes on its own. Every suggestion waits for you to approve, edit, or reject. - Approved context feeds your docs, llms.txt, AI chat, and MCP. ## From a support thread to your docs When a conversation is answered, Restless pulls out the part that applies to everyone and queues it for you to review. ### Answers become context When a support thread is answered or closed, Restless reads the back-and-forth and writes the reusable answer as a clean context item. The next person who asks finds it already written down. ### Pulled from resolved threads Extraction runs once a person has replied. An unanswered thread has no resolution to learn from, so it's skipped. ### You review before it ships Every suggestion lands in a Context inbox. Edit title and text, then approve or reject. Approved items stay private until published. ### A new item or an edit If the answer matches context you already have, Restless proposes an edit with a line-by-line diff. If it's already covered, it drops it. ### Public or private Publish an item to add it to your docs and llms.txt. Keep it private and it still answers questions over AI chat and MCP. ### Generic knowledge only It keeps endpoints, limits, auth, and what an error means. Personal and account details are scrubbed before anything is saved. ## Related features - [Human Support](https://www.restless.ai/human-support) — Where the answers come from. A resolved thread is what Restless learns from. - [Documentation](https://www.restless.ai/documentation) — Where approved context lands, served alongside your docs and llms.txt. - [Solicit feedback](https://www.restless.ai/solicit-feedback) — An MCP tool that lets agents send feedback on your API straight to your team. ## Setup Setup is a breeze. Restless is tightly integrated with your API, so we install a small SDK. Don't worry, we walk you through every step of the way. Run this in your API's repo: ```sh npx restless init ``` Or hand the setup to your coding agent with this prompt: ```text Set up Restless in this repo by running `npx restless init` and following the steps. ``` To try it on a demo API instead: ```sh git clone git@github.com:restlesshq/demo.git && cd demo && npx restless init ``` Nothing is uploaded without your permission. The CLI runs four steps: 1. **Map out APIs.** Locate your APIs, generate an OpenAPI (OAS) file, and write it to `.restless/`. An OAS file is the shape of your API: every endpoint, parameter, and response. Later steps use it to install the right adapter and wire up the middleware exactly. The scan points Claude Code, running locally on your machine, at your codebase to find your routes. Commit the `.restless/` folder along with your code; it's meant to live there. 2. **Install SDK.** The CLI detects the project runtime, selects its adapter, installs the Restless SDK and wires the request middleware. 3. **Test your setup.** Local traffic capture starts, and the CLI confirms requests are reaching Restless. 4. **Set up account.** Log in to claim your project on Restless. Privacy: scanning runs entirely on your machine via your own Claude Code install. We don't see a single line of your code, and nothing gets sent to our servers at that step. ## More from Restless - [Restless](https://www.restless.ai/index.md): Restless makes your API self-improving. Every API call, support question, and error leaves it better for the next request. - [Features](https://www.restless.ai/features.md): A new surface for your API: a public, LLM-first hub that gets every caller started and keeps them moving. - [Documentation](https://www.restless.ai/documentation.md): Restless generates your API documentation from your endpoints and the tools your team already uses, and keeps it current every time your API changes. - [Getting Started](https://www.restless.ai/getting-started.md): Onboarding is the most important part of your developer experience. Restless makes it easy for your developers to get their agent set up and ready to build. - [Agentic docs](https://www.restless.ai/agentic-docs.md): Restless isn't just agent-friendly docs. It's the only documentation platform built AI-first. There's a UI for humans, but the docs are shaped to make agents successful. - [Workbench](https://www.restless.ai/workbench.md): The Workbench sits at the bottom of your docs and gives developers a view into everything that's happening: view and filter logs, see what went wrong, and fix issues. - [Agent recovery](https://www.restless.ai/agent-recovery.md): When an agent hits an error on your API, it usually gives up and you never hear about it. Restless catches the failed call and tells the agent how to fix its request and retry. - [Human support](https://www.restless.ai/human-support.md): When a developer hits something AI can't fix, a human can step in and answer the question. Every answer becomes part of the context, and makes the next question easier! - [API Logs](https://www.restless.ai/logs.md): Your API is now how your users use your product. Restless brings every request into one place, so you can see which endpoints get hit, which calls fail, and where people give up. - [MCP server](https://www.restless.ai/mcp-server.md): Give agents the ability to do more than just write code. Give them access to do everything they need to build on your product, such as reading docs, debugging API calls and updating settings. - [AI Traffic](https://www.restless.ai/ai-traffic.md): Your API and docs get a lot of AI traffic now, and most of it is invisible. Restless shows you what AI is actually looking for, broken down by who is asking. - [Solicit feedback](https://www.restless.ai/solicit-feedback.md): When an agent hits something confusing in your API, it usually just gives up. Restless adds a send_feedback tool to your MCP server, so the agent can tell you what tripped it up. - [Sign up](https://app.restless.ai/signup)