Mintlify against GitBook on what an agent reads
In short
Mintlify hosts an llms.txt at the root of every docs project, lists every page, and keeps it current without maintenance; a custom llms.txt can replace it. Mintlify leads on llms.txt linking, 2 to 1; GitBook: The docs page links the files; a home page or header link by default is not documented.
The sourced difference
Mintlify answers Accept: text/markdown on the page URL and advertises llms.txt in an HTTP Link header on every response; GitBook documents the .md suffix, llms.txt, llms-full.txt and a per-site MCP server, but not header negotiation or a Link header on its LLM-ready docs page. Source, read 4 November 2026.
The rubric side by side
| Key | Mintlify | GitBook |
|---|---|---|
| Content in the initial HTML | 2, on by default | 2, on by default |
| Real status codes | 2, on by default | 2, on by default |
| llms.txt generation | 2, on by default | 2, on by default |
| llms.txt linking | 2, on by default | 1, with setup |
| Markdown on request | 2, on by default | 1, with setup |
| JSON-LD output | 1, with setup | 0, not offered |
| OpenAPI exposure | 2, on by default | 1, with setup |
| Fenced, tagged code | 2, on by default | 2, on by default |
| Total | 15 of 16 | 11 of 16 |
The two differ on 4 of the numeric keys: llms.txt linking, markdown on request, JSON-LD output, OpenAPI exposure. Evidence for each score is on the profiles of Mintlify and GitBook.
Verdicts by reader
- Technical SEO
- Mintlify gives a crawler more ways to find the agent files without guessing paths.
- Docs owner
- Both generate the files with no work; pick GitBook if an MCP endpoint per site matters more than headers.
- Front-end developer
- Mintlify needs no edge code for negotiation; on GitBook you rely on the .md URLs.
What each leaves undone
Mintlify
- Does not publish the llms.txt behind a fully authenticated site to tools that cannot sign in.
- Does not cap llms-full.txt size; the 100,000 character split applies to llms.txt only.
GitBook
- Does not exclude hidden pages from llms-full.txt or the MCP server.
- Does not document Accept-header negotiation on the LLM-ready docs page.
Work left to the developer: Mintlify, Low: write a description in each page frontmatter so llms.txt entries carry one. GitBook, Low: nothing to switch on; check hidden pages before publishing, since they appear in llms-full.txt.
Sources
- mintlify.com: the difference https://www.mintlify.com/docs/ai/llmstxt, read 4 November 2026
- Mintlify: documentation https://www.mintlify.com/docs/ai/markdown-export, read 4 November 2026
- GitBook: documentation https://gitbook.com/docs/publishing-documentation/llm-ready-docs, read 4 November 2026
Last reviewed 4 November 2026