03IMPROVE

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.

$ npx restless init
  • 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.

FULL STACK

From a supportthread 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.

DocsCharges

Rate limits

Requests are capped per key. Read the headers to see how much you have left before you hit a limit.

Support

Why do I keep getting 429s?

Back off and retry with an Idempotency-Key.

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

Where the answers come from. A resolved thread is what Restless learns from.

Learn more

Documentation

Where approved context lands, served alongside your docs and llms.txt.

Learn more

Solicit feedback

An MCP tool that lets agents send feedback on your API straight to your team.

Learn more

GET STARTED

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.

Nothing is uploaded without your permission.

$ npx restless init

A terminal animation shows the Restless API setup from introduction through account login.