How to Generate API Reference Pages from OpenAPI in Mintlify
Point Mintlify at your OpenAPI spec and it renders an interactive API reference with a working playground. Here is the snippet config, plus how to…
Mintlify is a documentation platform that turns MDX files and OpenAPI specs into a hosted docs site with built-in search, API playgrounds and an AI answers widget. The free Hobby plan covers 1 custom domain; paid Startup plans start around $150/month per project.
Mintlify targets the docs sites that developer tools need: sidebar navigation, a three-column API reference, searchable endpoints generated straight from your OpenAPI file, and code samples in six languages.
You write in MDX (Markdown with JSX), commit to a Git repo, and Mintlify builds and deploys on push. There is no CMS database and no theme PHP to maintain.
Hobby is free with one custom domain and Mintlify branding. Startup runs about $150/month per project with 5 editor seats and no badge. Growth is around $550/month with more seats and custom analytics. Enterprise pricing is quoted.
That is real money compared with a self-hosted Docusaurus site, which is free. The comparison only makes sense if you count the engineering hours you would spend building search, an API playground and the AI widget yourself.
Designed for API-first companies and developer tools with a handful of endpoints to a few hundred. If docs are a growth channel for you, the polish is worth the price.
Limits worth knowing. The MDX requirement means non-technical writers need Git, or at least a PR workflow they tolerate. Customisation is bounded — you get props on components, not a full template system, so a heavily branded docs site will fight the defaults.
Also, versioning is per-path and gets awkward past three live versions. Teams maintaining five SDK versions often end up with a hand-rolled redirect matrix.