For sites that want to be read by AI
Build llms.txt and llms-full.txt from the pages you already have
List your documentation's pages, turn each into Markdown, and assemble the two files AI assistants look for.
The problem
llms.txt is a short index of your important pages written for language models, and llms-full.txt is the content itself in Markdown. Written by hand, both are stale by the next release, and a generic HTML-to-text converter keeps your navigation menus and loses the structure that made the docs readable.
How domscout handles it
POST /map lists the URLs under your docs path, from the sitemap and from links. POST /scrape with renderJs: false then turns each page into Markdown from one fast HTTP request, keeping headings, lists, links and code blocks; tables come through as plain rows, so capture table-heavy pages with the browser instead. Check metadata.contentQuality and retry with the browser for any page that came back thin. Write each page's title and a one-line description into llms.txt, join the Markdown into llms-full.txt, and regenerate both on every docs deploy.
Where it shows up
- llms.txt and llms-full.txt regenerated by the docs build.
- A Markdown copy of each docs page, served next to the HTML.
- The same Markdown fed into your own assistant's index.
The request
POST /scrape. /scrape is on every plan at 1 credit a page. /map, for the list of URLs, starts at Pro and costs 2 credits; if you already have a sitemap, you can read the URLs from it instead.
Go further
More in AI and agents: Web access for AI agents · Screenshots for vision models · Rendering generated HTML · Coding agents checking their work · Newsletter curation · FAQ drafts from documentation · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.