Why Mintlify Scores 66: The Documentation Platform That Helps Others Score Higher
Mintlify is the documentation platform behind Anthropic, Supabase, Cursor, and hundreds of other developer companies. It makes API docs beautiful, searchable, and structured — all things that improve agent readiness scores. But Mintlify itself scores 66 Silver. The irony: a company that helps others become agent-discoverable has the same gaps as everyone else.
Score Overview: 60/100 Silver
Mintlify's score of 60 places it in the Silver tier (60-74), nine points below the Gold threshold. This is a strong score for a SaaS platform — above the 500-business average of 43 — but surprising for a company whose entire product is making technical services more discoverable and documented.
The strengths are real: Mintlify has a clean REST API, excellent data quality, reliable infrastructure, and solid security. These are the table-stakes dimensions where well-run developer tools consistently perform. The weaknesses are equally revealing: enterprise pricing is hidden, payment is not programmatic, and there is zero agent-native infrastructure.
Dimension-by-Dimension Breakdown
Nine dimensions scored. Six above average, one at average, two below. Here is the full breakdown.
The pattern: Mintlify excels at everything that requires engineering discipline — API design, data quality, security, reliability. It falls short on everything that requires a deliberate agent-economy strategy — agent-native files, transparent pricing, and MCP infrastructure. This is the most common pattern in Silver-tier developer tools.
The Irony: Helping Others Score Higher Than Yourself
Mintlify's product directly improves D2 API Quality and D6 Data Quality scores for every company that uses it. Companies that generate docs through Mintlify typically score 5-10 points higher on these dimensions than companies with hand-written documentation. But Mintlify has not applied the same approach to its own agent readiness.
Here are four specific ironies — and what Mintlify could do about each one overnight.
Mintlify helps customers create OpenAPI docs
But...
Mintlify's own OpenAPI spec is not published at a standard discovery path
Fix (overnight)
Publish /openapi.json or /.well-known/openapi.json
Mintlify renders beautiful structured docs
But...
No llms.txt file that points agents to that documentation
Fix (overnight)
Add /llms.txt with a link to their own docs — they literally generate this for customers
Mintlify supports custom MDX components
But...
No agent-card.json declaring Mintlify as a service agents can use
Fix (overnight)
Create /.well-known/agent-card.json with their API capabilities
Mintlify has a REST API for managing docs
But...
No MCP server exposing those same capabilities to AI agents
Fix (overnight)
Wrap existing API endpoints as MCP tools — their API is already structured for it
The gap is not technical. Mintlify has the engineering talent, the API infrastructure, and the domain expertise to close every one of these gaps in a single sprint. The gap is strategic — documentation platforms have not yet positioned themselves as agent-readiness infrastructure, even though that is exactly what they are becoming.
Mintlify's Path to Gold (75+)
Mintlify needs 9 points to reach Gold. Here are the highest-value changes, ranked by point impact.
Add agent-card.json
+3-4Effort: LowDeclare Mintlify as a service agents can use. List API capabilities, supported auth methods, and service description. One JSON file at /.well-known/agent-card.json.
Add llms.txt
+1-2Effort: LowPoint agents to Mintlify's own documentation. Mintlify literally helps customers create the content that llms.txt links to — adding their own is one line of work.
Publish transparent pricing
+2-3Effort: LowMake enterprise pricing visible or at least provide a pricing range. Agent procurement tools need structured pricing data to compare vendors programmatically.
Create an MCP server
+3-5Effort: MediumWrap existing API endpoints (create_page, update_content, deploy_docs, search_docs) as MCP tools. Mintlify's REST API is already well-structured — the MCP wrapper is mostly mapping.
Add security.txt
+1Effort: LowStandard /.well-known/security.txt with contact info and PGP key. Quick win for D7 Security scoring.
Total estimated improvement: +10-15 points. Four of five actions are low effort. The MCP server is the only medium-effort item, and Mintlify's existing API makes it straightforward. A focused sprint could take Mintlify from 66 Silver to 76-81 Gold — turning a developer tool into an agent-native platform.
What This Means for Documentation Platforms
Mintlify is not alone. ReadMe, GitBook, Docusaurus, and every documentation platform faces the same gap: they help customers become more discoverable by agents but have not made themselves agent-discoverable. This is a category-wide blind spot.
The documentation platform that closes this gap first gains a powerful positioning advantage: “We do not just help you write docs — we make your entire service agent-ready.” Mintlify is best positioned to claim this because their product already generates the files agents need (OpenAPI rendering, structured content, search indexes). They just need to generate those files for themselves and add the agent-native layer on top.
The documentation-to-agent-readiness pipeline is the most natural product extension in the developer tools space. The company that ships it first owns the category definition.
Docs platforms are agent-readiness infrastructure
Structured API docs, OpenAPI specs, and search indexes are core inputs to agent readiness. Documentation platforms are already 60% of the way to being agent-readiness platforms.
The missing 40% is agent-native files
agent-card.json, llms.txt, MCP server generation, and pricing transparency. These are product features, not engineering challenges. Whoever ships them first defines the category.
Customer value multiplier
If Mintlify generated agent-card.json and llms.txt alongside docs, every Mintlify customer would see their agent readiness score increase. That is a measurable, sellable outcome.
MCP server generation is the endgame
Documentation platforms that auto-generate MCP servers from OpenAPI specs become the single tool that takes any API from invisible to agent-ready. That is a massive product expansion.
Frequently Asked Questions
What is Mintlify?
Mintlify is a documentation platform used by developer-focused companies to create, host, and maintain API documentation. It takes OpenAPI specs and MDX content and generates polished, searchable documentation sites. Companies like Anthropic, Supabase, and Cursor use Mintlify for their public docs.
Why does Mintlify only score 66?
Mintlify scores well on technical fundamentals — API quality, data structure, security, and reliability — because it is a well-engineered developer tool. It loses points on D4 Pricing (enterprise pricing is hidden), D5 Payment (no programmatic subscription management), and D9 Agent Experience (zero agent-native files). The last gap is ironic because Mintlify helps other companies create the structured documentation that improves agent readiness.
Could Mintlify reach Gold score?
Yes, and faster than almost any other company. Mintlify already has a clean REST API, structured documentation, self-service onboarding, and developer-focused infrastructure. Adding agent-card.json, llms.txt, and transparent pricing would add roughly 10-15 points, pushing past the Gold threshold of 75. Adding an MCP server wrapping their existing API would push even higher. The infrastructure gap is small — it is just not built yet.
How does Mintlify help other companies score higher?
Mintlify improves D2 API Quality and D6 Data Quality scores for its customers by generating structured, searchable, versioned API documentation from OpenAPI specs. Good documentation makes APIs more discoverable and usable by agents. Companies using Mintlify for their docs typically score 5-10 points higher on these dimensions than companies with hand-written or wiki-based documentation.
What would a Mintlify MCP server look like?
A Mintlify MCP server would expose tools like create_page (add a docs page), update_content (edit existing docs), deploy_docs (trigger a deployment), search_docs (full-text search across a project), and get_analytics (page views, search queries, 404 errors). These map directly to their existing REST API endpoints. An AI agent could then manage documentation as part of a CI/CD pipeline without human intervention.
How does your documentation platform score?
Whether you use Mintlify, ReadMe, GitBook, or custom docs — see how your agent readiness compares across all 9 dimensions. Free scan, 60 seconds.