Mintlify turns docs into infrastructure
$21.4M/year Vercel of developer docs
Mintlify is winning because developer docs are starting to act less like a help center and more like a machine interface that determines whether an API gets used at all. Once Claude Code, Cursor, and similar tools become the first reader, the important job of docs shifts from explaining concepts to exposing structured pages, API schemas, search, and MCP endpoints that an agent can reliably fetch, parse, and act on.
-
Earlier docs tools were built mainly for humans reading a polished site. ReadMe centered on API reference generated from OpenAPI and a managed developer hub. Mintlify kept that polish, but added a Git based workflow plus hosted MCP and llms.txt style discovery so agents can search docs, retrieve full pages, and in some cases act on them inside coding tools.
-
That changes the buying logic for customers. A docs team is no longer just trying to reduce support tickets. It is trying to make sure an agent inside Cursor or Claude Code can find the right auth flow, copy the right endpoint, and generate working code without sending the developer to search elsewhere.
-
The closest analogy is infrastructure like Vercel or Supabase, where the product wins by being the default layer machines interact with. Mintlify serving Anthropic, Cursor, Replit, Lovable, and Vercel, while agent traffic rose from roughly 15% in January 2026 to 66% by July 2026, shows docs are becoming part of the runtime path for AI assisted software creation.
The next step is that documentation platforms become two way systems. They will not just publish pages for humans and agents to read, they will expose live context that agents use to choose tools and open pull requests to improve docs themselves. That pushes developer documentation closer to core product infrastructure, and away from marketing or support software.