Let AI assistants answer your users from your docs.
Developers ask ChatGPT, Claude and Cursor before they open your docs. When those assistants cannot read your pages properly, they make an answer up. aireadify turns a documentation site into a hosted endpoint agents can search and cite. Just the URL, no code changes.
Three invisible support costs.
Wrong answers
Assistants stitch answers from stale tutorials and forum posts. Users follow them, fail, and file a ticket or give up.
Half-read pages
Navigation and scripts eat most of the tokens in a docs page. The assistant truncates halfway, and the missing part is the parameter that mattered.
Not found
Without llms.txt or a markdown version, agents guess URLs. You shipped a feature; the model still does not know.
A URL, three steps, one afternoon.
Read the docs
Pages are discovered from sitemap.xml or llms.txt, fetched, split by heading and indexed. Refreshed hourly, from 200 pages.
Generate the endpoint
A hosted MCP endpoint at mcp.aireadify.ai/your-docs, with server card, OpenAPI and llms.txt generated alongside.
Connect agents
Claude, Cursor and ChatGPT add the endpoint directly. Then put the chat widget back on your docs; every answer links its source page.
Three read-only tools that cover what developers ask most.
search_docs
Full-text search; returns the best matching sections with snippet and deep link.
get_page
One page as clean Markdown, navigation and scripts removed.
list_pages
Indexed pages with descriptions, filterable by path prefix.
Docs behind login, version switching and tools that call your API come in phase two.
Do I need to change my docs site?
No. We only read public pages. To let agents discover the endpoint on your own domain, add one redirect or copy the server card; the report shows exactly how.
Which docs frameworks are supported?
Any site with a sitemap.xml or llms.txt: Docusaurus, VitePress, Mintlify, GitBook, Nextra, MkDocs and ReadMe all tested. Without either, pages are discovered from homepage links.
Will the answers make things up?
The chat widget answers only from retrieved sections and links the source page on every answer. When the docs do not cover something it says so and points to the closest page.
What does it cost?
The scan is free. A hosted MCP endpoint is $79 per month per site and includes Ready Kit; the chat widget is $49 per month per site. During early access the endpoint is free for the first 90 days.
First, see how your docs look to an agent.
30 seconds, free, no signup. Documentation sites are scored with documentation weighting.