Docs & Help

Vital signs

Why it's on the table

On the table, Docs & Help (Dc) is seat 36 of 58, in the Support & Success family. It is a stable element — the category has settled, choosing is cheap, and switching is rare. Pick a holder and move on; this is not where your decision budget should go. It is marked essential: a company that leaves this seat empty is running with a gap that compounds. It sits in the lowest paid band — lunch money against the hours it returns.

Docs & Help: the top 5 — v2026.Q3

Edition v2026.Q3 · ranking, pricing and status verified 2026-08-06.

1. 1MintlifyMintlify (YC W22)

   Starter free (5 seats, MCP server, API playground) · Pro paid/deployment + 10k AI credits, $0.01/credit overage · Enterprise custom

   Best for The default docs element for an AI-led startup — agent-readable by default (llms.txt, .md routes, hosted MCP), with the data to prove agents actually use it.

   The category's center of gravity: 5,000+ hosted docs sites, Anthropic/Claude Code among its docs customers, $10.6M→$21.4M ARR in seven months (Jul 2026), and a $45M Series B at $500M led by a16z (Apr 14, 2026). Its July 2026 traffic report is the defining dataset of the era — agents at 66% of docs traffic and climbing — and Mintlify Index (Aug 6, 2026) turns those 5,000 sites into one retrieval layer for coding agents.

   Watch Pro price is animated off the pricing page — budget clarity requires a sales touch; credit-metered AI features add bill variance. Its own benchmark data doubles as marketing; the 66% figure is Mintlify-network-only, not the whole web.

   $45M Series B at $500M valuation, led by a16z; $67M total raised (Apr 14, 2026) [src] · Agents = 66% of docs traffic across Mintlify sites, up from 15.2% in Jan 2026; 213M agent requests vs 105M human loads (Jul 2026) [src] · $21.4M ARR Jul 2026 (vs $10.6M end-2025), 150% NRR, 10k+ companies (Sacra) [src]
   Site →Docs →

2. 2GitBookGitBook

   Free · Premium $65/site/mo · Ultimate $249/site/mo (+$12/user) · Enterprise custom (annual = 2 months free)

   Best for Teams where PMs, support, and engineers all edit docs — visual editor plus Git sync, with llms.txt and an MCP server on every tier including free.

   The classic, repositioned smartly for 2026: 2M+ users, and its pitch — "AI made docs easy to write. Not easy to trust." — attacks the failure mode agent-era docs actually have, drift and amplified errors. LLM optimization (llms.txt, llms-full.txt, .md routes) and an auto-generated MCP server ship on all tiers; the GitBook Agent detects stale content and AI Insights shows where humans and agents get stuck.

   Watch The good AI (AI Assistant, Insights, adaptive content) is gated behind the $249/mo Ultimate tier, and per-site pricing stacks up across multiple products. No published traffic data comparable to Mintlify's; less gravitational pull among AI-native startups.

   "Used by more than two million people" — Zoom, FedEx, Nvidia, Snyk among customers (Aug 2026) [src] · llms.txt, llms-full.txt, .md versions and auto MCP server on every tier incl. free (pricing page, Aug 2026) [src] · GitBook Agent + AI Insights positioned as the docs 'trust layer' (homepage, Aug 2026) [src]
   Site →Docs →

3. 3FernBirch Solutions → Postman (acquired Jan 2026)

   Hobby free · Team $150/mo (annual) · Enterprise custom; AI credits tiered (250/1,000/custom)

   Best for API-first companies that want docs, SDKs in 9 languages, llms.txt, and an MCP server all generated from one OpenAPI/AsyncAPI/gRPC spec.

   The spec-to-everything play: one API definition yields reference docs, client SDKs, Ask Fern answers (890k+ served), and a queryable MCP server. Powers ElevenLabs (1.5M unique docs users/mo), Auth0, Webflow, Square. Postman acquired it on Jan 8, 2026 with brand and roadmap kept intact — plugging Fern into a 500k-company distribution machine.

   Watch Acquisition risk cuts both ways: Postman promises independence, but roadmaps bend toward owners. Guide-style, non-API documentation is weaker than Mintlify/GitBook; customer-count claims vary wildly (homepage "8,000+ customers" vs Postman's "over 200 customers" — the latter is likely paying).

   Acquired by Postman, Jan 8, 2026 — 25-person team joins, brand/roadmap unchanged, 200+ customers cited [src] · 890,491 Ask Fern answers, 13,392 SDKs generated; ElevenLabs 1.5M unique docs users/mo (homepage, Aug 2026) [src] · Team $150/mo annual; llms.txt + MCP server generation on all paid tiers (Aug 2026) [src]
   Site →Docs →

4. 4ReadMeReadMe (YC W15)

   Starter free · Pro $250/mo · Enterprise $3,000+/mo · Ask AI add-on $150/mo

   Best for Enterprise API programs that want a decade-proven platform — interactive API explorer, git-native review flow, and agent read/write access to docs via MCP.

   The API-docs veteran (NVIDIA, Amazon, PagerDuty) that re-platformed for the agent era: llms.txt and MCP servers on every tier including free, an AI Writer that proposes doc updates from your PRs, and MCP write access so Claude Code or Cursor can update docs directly from CI. "Documentation built for agents" is now the homepage headline.

   Watch Priciest entry of the top five once you leave the free tier — $250/mo plus $150/mo for Ask AI — and enterprise starts at $3k/mo. Independent and profitable-quiet rather than momentum-loud; less pull with new AI-native startups than Mintlify.

   llms.txt + MCP server on all tiers; Ask AI $150/mo add-on; Pro $250/mo, Enterprise $3,000+/mo (Aug 2026) [src] · MCP write access: "Update your docs from Claude Code, Cursor, or CI" (homepage, Aug 2026) [src] · Customers include NVIDIA, Amazon, PagerDuty (homepage, Aug 2026) [src]
   Site →Docs →

5. 5DocusaurusMeta (open source, MIT)

   Free, MIT-licensed · you pay only for hosting (Vercel/Netlify/GitHub Pages)

   Best for Engineer-written docs with zero platform spend and total control — React/MDX, versioning, i18n, and a community llms.txt plugin.

   The open-source default: 65.1k GitHub stars, 12.2k dependent projects, actively shipped by Meta (v3.10.1, Apr 30, 2026). Everything the SaaS platforms charge for — versioning, localization, search — is free; the agent layer (llms.txt generation, MD routes) arrives via community plugins listed on llmstxt.org.

   Watch You are the platform team: no hosted MCP server, no AI assistant, no agent analytics out of the box — each is a plugin or a build-it. Docs-site maintenance is exactly the kind of undifferentiated work an AI-led startup should be buying, not building.

   65.1k stars, 12.2k dependents; v3.10.1 released Apr 30, 2026 [src] · Maintained by Meta Open Source; v3.10 current (site, Aug 2026) [src] · Community llms.txt plugin listed in the official llms.txt ecosystem (Aug 2026) [src]
   Site →Docs →

Docs & Help: the top 8 compared

Edition v2026.Q3 · ranking, pricing and status verified 2026-08-06.

How to choose your docs & help

If you're an AI-native startup shipping your first docs site this quarter

Mintlify Starter — free, and llms.txt, .md routes, MCP server, and API playground are defaults, not add-ons. You inherit the network Claude Code's own docs team uses.

If half your doc edits come from support, PMs, or founders who won't touch MDX

GitBook — the visual editor plus Git sync bridge, and its stale-content agent guards the accuracy problem AI writing creates. Budget for Ultimate if you want the AI features.

If you sell an API and are hand-maintaining SDKs alongside docs

Fern — one spec generates both, plus an MCP server agents can execute against. Price in the Postman-ownership question before a multi-year commitment.

If docs traffic and agent 404s matter to you (they should)

Ship llms.txt and markdown routes whatever platform you choose — Mintlify's 2,400-run benchmark (Jul 2026) showed a single llms.txt link cuts agent 404s by ~90% (2.23 → 0.11 per run).

If budget is zero and your engineers already write markdown in the repo

Docusaurus with the llms.txt plugin — then reevaluate the day docs maintenance shows up in sprint planning, because that's work the paid platforms have automated.

Docs & Help: the whole field

17 more tools tracked in this category, including 4 dead, renamed, or sunsetting — a reference that hides the graveyard isn't one. Verified 2026-08-06.

Docs & Help: the category in numbers

Edition v2026.Q3 · ranking, pricing and status verified 2026-08-06.

• Agents overtook humans on docs: 66% of measured traffic across Mintlify-hosted sites in Jul 2026 (213M agent requests vs 105M human loads), up from 15.2% in Jan 2026 — trajectory points at ~90% by year-end [src]
• Mintlify raised a $45M Series B at $500M led by a16z (Apr 14, 2026); ARR $10.6M (Dec 2025) → $21.4M (Jul 2026), 150% NRR [src]
• Consolidation wave: Postman acquired Fern (Jan 8, 2026), Mintlify acquired Trieve (Jul 2025), SmartBear absorbed Stoplight (2024) — docs platforms are becoming API-platform features [src]
• llms.txt (proposed by Jeremy Howard / Answer.AI, Sep 2024) became table stakes: shipped by default on Mintlify, GitBook, Fern, ReadMe, and Read the Docs; public directory lists 1,458 adopters incl. Anthropic, Cloudflare, Perplexity (Aug 2026, a known undercount) [src]
• Measured payoff of agent-readable routes: a single llms.txt link cut agent 404s ~90% (2.23 → 0.11 per run) in Mintlify's 2,400-run, 20-site benchmark (Jul 2026); 83.7% of agent requests already use explicit machine routes [src]
• Hosted MCP servers for docs went from novelty to default in under a year — GitBook, ReadMe, and Mintlify include them on free tiers; Mintlify Index (Aug 6, 2026) aggregates 5,000+ docs sites into one agent retrieval layer [src]

Docs & Help: method & sources

Ranking criteria: agent-readability by default (llms.txt, .md routes, MCP), momentum with AI-native startups, pricing accessibility, and evidence discipline of vendor claims. Caveats: (1) Mintlify's Pro price is rendered as an animated counter on its pricing page and is not stated in its docs — we could not pin the dollar figure from primary sources; confirm before budgeting. (2) The headline 66%-agent-traffic stat is Mintlify's own network data — directionally corroborated by its earlier Series B claim of ~50% (Apr 2026) but not independently audited. (3) Customer-count conflicts: Mintlify Series B post says 20,000+ companies vs Sacra's 10,000+ (we cite Sacra as the more conservative); Fern homepage claims 8,000+ customers vs Postman's 200+ at acquisition (likely free vs paying — we cite Postman's figure). (4) Document360 no longer publishes prices; treat all quote-based vendors as enterprise-sales motions. Adjacent elements: AI support agents that answer tickets (Fin, Decagon, Sierra — and increasingly Inkeep) belong to Sa · Support Agent; internal wikis and team knowledge (Notion, Obsidian) belong to Kw · Knowledge Wiki; kapa.ai sits on the Dc/Sa border — it reads docs (Dc) to deflect tickets (Sa) — and we keep it in Dc's field as the docs-answer layer. Ranking criteria: verified commercial traction, independent satisfaction surveys, agent benchmarks, and founder-fit (price floor, lock-in, surfaces). Editorial, never paid — the charter. Machine-readable twin: dc.json.

Our take

Your docs are now read by more agents than humans. Structure accordingly — it feeds your support element directly.

Combines with

Appears in compounds

The Trust Stack