Skip to content
All comparisons

API documentation tools, compared

Every tool here renders an OpenAPI file well. They differ in where the content comes from, how a version is made, and who can read it, people and AI agents alike.

8 products, compared from their own documentation.

The products, one by one

What each is, its strong points, its limits, and who it suits.

APIGit

A Git-native platform for API design, documentation, mock servers and governance

APIGit publishes a documentation site from a commit: OpenAPI, AsyncAPI and GraphQL references and Markdown guides in one navigation. A version is a name pointing at a commit, so readers see exactly what was reviewed and merged.

Best for:
Teams whose docs should always match a reviewed commit
Price:
Free for one user. Team: $24 a month, 3 seats included; $8 per further seat.

Strong points

  • Publishing builds nothing: a version points at a commit, or follows a branch
  • References and Markdown guides in one site, with seven themes
  • Private versions: members, named external viewers or password links
  • llms.txt, Markdown pages and an MCP server for every published document

Limits

  • No usage analytics of readers or API keys shown in the docs
  • Guides use a built-in set of Markdown components; no custom MDX or React pages

Mintlify

A documentation platform for product and API docs, by Mintlify

Mintlify builds documentation sites from MDX files in your repository, with a visual web editor, a preview for each pull request and AI features throughout. The API reference is rendered from your OpenAPI file with a live playground.

Best for:
Product documentation where the API reference is one section
Price:
Free for five editors. Pro $450 a month billed yearly.

Strong points

  • MDX components and a visual editor for writers
  • An AI assistant, writing agents, llms.txt and a hosted MCP server
  • Five editors and a custom domain on the free plan
  • Docs stay in your GitHub or GitLab repository

Limits

  • Renders an OpenAPI file but does not edit, lint or mock it
  • Pro is $450 a month billed yearly; previews and password protection start there

Postman

An API client and testing platform, by Postman, Inc.

Postman publishes documentation from a collection, with code samples and a Run in Postman button that opens the requests in the client. It suits APIs whose readers are Postman users.

Best for:
Public APIs whose users start from Postman
Price:
Free for one user. Solo $9 a month and Team $19 per user a month, billed yearly.

Strong points

  • Run in Postman puts working requests in a reader's client
  • Custom domains on paid plans
  • A very large public API network for discovery

Limits

  • Published documentation is public to anyone with the link
  • Documentation follows the collection rather than an OpenAPI reference with guides

SwaggerHub

An API design platform, now named Swagger Studio, by SmartBear

Documentation in SmartBear's suite is Swagger Portal, a separate product that publishes APIs from the registry with Markdown pages, a try-it console and public or private access.

Best for:
Teams that already design in Swagger Studio
Price:
Individual, Team, Enterprise and Enterprise Plus plans; prices are not published.

Strong points

  • Publishes straight from the design registry
  • Private portals with your own identity provider
  • Part of a suite with testing and a catalog

Limits

  • A separate product from the design tool
  • A custom domain is Enterprise only

Stoplight

An API design and documentation platform, by SmartBear

Stoplight publishes hosted documentation from a project: API references with a try-it console beside Markdown guides, public or private.

Best for:
Teams that design in Stoplight and publish from the same project
Price:
Free for one user and one project. Basic $44 a month billed yearly with three users.

Strong points

  • References and Markdown guides together
  • The open-source Elements components to embed docs yourself
  • Private docs, with SAML single sign-on on higher plans

Limits

  • A custom domain starts on the Startup plan
  • No MCP server or AsyncAPI reference is documented

Apidog

An all-in-one API design, debugging, testing, mock and documentation platform, by Apidog

Apidog publishes documentation sites from a project, with Markdown pages, versions, a Try it out console and a custom domain, and it has more ways to restrict access than most tools here.

Best for:
Teams already designing and testing in Apidog
Price:
Free for up to four users. Basic from $9 per user a month.

Strong points

  • Password, IP allowlist, email allowlist and custom login
  • Try it out, versions and Markdown pages
  • llms.txt for published sites

Limits

  • Content comes from the Apidog project rather than files in Git
  • AsyncAPI is not among the documented formats

Redocly

An API documentation platform, with the open-source Redoc and Redocly CLI, by Redocly Inc.

Redocly is the documentation specialist here. It builds a site from a Git repository with API references, Markdoc and React pages, a Replay console and a preview for every pull request.

Best for:
Developer portals with custom pages and many contributors
Price:
No free hosted plan. Pro $249 a month billed yearly, unlimited seats. Redoc and Redocly CLI are free and open source.

Strong points

  • Markdoc and React pages for custom portals
  • A preview and a visual diff for every pull request
  • Custom domain and MCP server on every plan
  • The open-source Redoc renderer if you self-host

Limits

  • No free hosted plan; Pro is $249 a month billed yearly
  • SSO and role-based access start on Scale

ReadMe

A hosted developer hub for API documentation, by ReadMe

ReadMe is a developer hub more than a renderer: guides in a visual editor, an API reference with authenticated Try It, a changelog and usage metrics, with optional two-way sync to Git.

Best for:
Companies whose docs are written by a mixed, partly non-technical team
Price:
Free for one admin and one project. Pro $250 a month billed yearly.

Strong points

  • A visual editor that non-technical writers can use
  • Readers see their own API keys and request history
  • Custom domain and Git sync on the free plan
  • Usage metrics, changelog and forums

Limits

  • Content lives in ReadMe's store; Git is a sync
  • No AsyncAPI, and no mock server or design governance
  • Pro is $250 a month billed yearly; private docs start there

Side by side

Each product name opens its full comparison with APIGit.

FeatureAPIGitMintlifyPostmanSwaggerHubStoplightApidogRedoclyReadMe
Git and version control
Where your API files liveYes:Its own Git repositoryYes:Your repoPartly:Postman Cloud, or your repoNo:Its own registryPartly:Your repo, or StoplightPartly:Its own project storeYes:Your repo, or Redocly'sPartly:Its own store, synced
Clone and push with any Git clientYes:HTTPS and SSHPartly:Through your Git hostNo:Not a Git hostNo:Not a Git hostNo:Through your Git hostNo:Not a Git hostPartly:Through your Git hostNo:Through your Git host
Branches and tagsYes:Git branchesYes:Git branchesPartly:Forks; Git via your repoNo:Its own versionsYes:Git branches, paidPartly:Its own sprint branchesYes:Git branchesPartly:Its own, per version
Pull requests and reviewYes:Built inYes:On your Git hostPartly:On forked collectionsPartly:Comments, no PRsPartly:On your Git hostPartly:Its own merge requestsYes:Built in, with previewsPartly:Review tab; no PRs
Commit history and diffYes:Every commitPartly:Diff viewsPartly:Diff in its pull requestsPartly:Version comparePartly:On your Git hostPartly:Per endpointPartly:Diff; partial historyPartly:Page history
Working with GitHub, GitLab and othersYes:Optional syncYes:GitHub, GitLabYes:Native GitPartly:Push; pull on EnterpriseYes:Four providersPartly:Spec-first mode, betaYes:Four providersYes:Two-way sync
Documentation
Hosted documentationYes:From a commitYes:MDX sitesYes:From a collectionYes:Swagger PortalYes:Hosted docsYes:Hosted sitesYes:Markdoc and ReactYes:Developer hub
Custom domainYes:Team and upYes:Every planYes:Paid plansPartly:Enterprise onlyYes:Startup and upYes:Custom domain for a documentation siteYes:On every planYes:Every plan
Try it consoleYes:Try It Out for OpenAPI, on every planYes:An API playground that sends live requestsPartly:Run in Postman opens the collection in the clientYes:A try-it console in the portalYes:Try it in the hosted docsYes:Try it out in the published documentationYes:The Replay consoleYes:Try It, with the reader's own API keys and request history
Private documentationYes:Members only, named external viewers, or a password-protected linkYes:Login for your organization on every plan; password on Pro; OAuth and JWT on EnterpriseNo:Published documentation is available to anyone with the linkYes:Public or private portals, with your own identity providerYes:Private or public docs; SAML single sign-on from Pro TeamYes:Password; IP allowlist, email allowlist and custom login on Professional and aboveYes:Login-protected docs on Pro; SSO and role-based access on ScaleYes:Private docs on Pro; SSO and roles on Enterprise
CLI and AI agents
Command lineYes:apigitYes:mint: local preview, validate, broken-links, accessibility checks, deploy and exportYes:postman: collection run, spec lint, workspace push, monitor and performance runsYes:swaggerhub-cli: create, update and publish APIs and domains, manage integrations and rule setsPartly:@stoplight/cli publishes a directory to a project; Spectral and Prism have their own CLIsYes:apidog-cli: run tests, import, export, branches, merge requests, docs sites and mocksYes:redocly: lint, bundle, split, join, build-docs, preview, respect and more; open sourceYes:rdme uploads OpenAPI and Markdown, also as a GitHub Action
MCP serverYes:Docs and accountYes:For docsYes:For the accountYes:For the accountNot coveredYes:BetaYes:For docsYes:For docs
  • Yes:Has it
  • Partly:Has part of it; the cell says which
  • No:Does not have it

Scroll sideways for every product.

How to choose

Decide what a version is

A version tied to a commit can be reviewed before it goes live and reproduced later. A version edited in place cannot.

List your readers

Partners behind a login, the public on your domain, and agents that read Markdown or MCP are three audiences with different needs.

Keep guides beside references

Guides drift when they live in a different tool from the spec. One source for both keeps them in step.

Questions

Which API documentation tools were compared?
APIGit, Mintlify, Postman, SwaggerHub, Stoplight, Apidog, Redocly and ReadMe. They were chosen because teams that work with OpenAPI most often weigh them against each other. The page is published by APIGit, so APIGit is listed first; the limits of each product, ours included, are listed beside its strong points.
Where do the facts come from?
From each vendor's own public documentation and pricing pages, listed under the table with the date they were read. APIGit's entries follow our documentation and pricing page.
Why does the comparison start with Git?
Because an API description is a file that several people change, and Git is the tool built for that. A tool that keeps the file in a real Git repository gives you branches, review and history without a sync step; a tool with its own store has to rebuild those things or copy the file out.
Can I use more than one of these tools?
Yes, and many teams do. Because an APIGit project is an ordinary Git repository, any tool that reads OpenAPI files from Git or from a folder on your machine can work with the same files.

Other jobs: API design tools, API mocking tools.

Try it yourself

Worked examples from the learn hub, each with the output of the tools.

Put your API and docs in a repository today

Create a free workspace, add an OpenAPI file and a Markdown guide, and publish your first documentation site and mock server in minutes.

Free for individuals. No credit card.

$ npm install -g @apigit/cli$ apigit auth login$ apigit doc publish