Make your product easy for AI agents to find, trust, and use.
SaturnDocs publishes your documentation as a human-readable site, Markdown, llms.txt, Model Context Protocol, WebMCP, agent skills, Agent2Agent, search, and cited answers. Agents get the product context and technical instructions they need to recommend your product and finish the task.
Agents need to know when to recommend your product and how to use it.
Product overviews and use cases help an agent decide whether your product fits the user’s needs. Guides, API references, and troubleshooting steps help it complete the work. SaturnDocs makes both kinds of information directly available through structured pages, machine-readable indexes, Model Context Protocol retrieval, stable URLs, and answers with citations.
llms.txt points agents to the right page.
Every SaturnDocs customer site publishes llms.txt as a concise index and llms-full.txt as consolidated context. These files identify the organization, describe the documentation, and link to canonical pages. Visible links make the files discoverable to agents that browse the site instead of probing known root paths.
The files are generated from the same content data that drives the site, so feature descriptions, page links, and canonical URLs do not drift into a second hand-maintained version.
docs.yourcompany.com/llms.txt
in the footerllms.txtConcise index of every canonical page
publishedllms-full.txtConsolidated context in one file
publishedguides/webhook-signing.mdMarkdown mirror of every page
publishedGenerated from the same source as the site
The MCP server retrieves relevant documentation.
The documentation MCP server gives compatible agents a structured search path. An agent can ask for a setup step, endpoint, configuration field, or error, retrieve the relevant published material, and keep the source location attached to the result.
Citations connect each answer to its source.
A citation makes an answer inspectable. It shows which published page supports the response, lets the reader inspect prerequisites and warnings, and exposes missing documentation when no source contains the answer. SaturnDocs treats that missing answer as a specific page or revision to produce.
Read the detailed explanation in Inside the docs assistant, or see every included machine surface on Platform.
>Which scope does a webhook subscription need?
●Search published documentation
●Read guides/webhook-subscriptions.md
A subscription needs the webhooks:write scope. Create the endpoint first, then subscribe, or the request returns 403.
↳ guides/webhook-subscriptions.md
Every answer carries the page that supports it
Frequently asked questions.
What is llms.txt?
llms.txt is a plain-text map of a documentation site for AI tools. It identifies the organization and links to durable pages with short descriptions. SaturnDocs publishes it automatically from the same source as the human-readable site.
What does the documentation MCP server do?
The MCP server gives compatible AI agents a structured way to search the documentation and retrieve relevant material while they work. It returns information from the current documentation source rather than from a separate hand-maintained copy.
How does the SaturnDocs assistant avoid guessing?
The assistant answers from the published documentation and cites the pages that support its response. If the documentation does not contain enough information, the assistant says so instead of filling the gap with an unsupported answer.
Can AI agents access private documentation?
Only when they use an authenticated path that grants access to the protected material. Public machine-readable surfaces expose public documentation; private content remains subject to the same reader permissions as the site.