Mintlify on X

Praise is mostly about the output rather than the AI. People call the docs' visuals Stripe-like, say the editor experience is improving fast, and count small wins like a hotkey that works. A developer describing OpenAPI 3.2 support says the upgrade is a spec bump, backward compatible with 3.1, so you can "just bump your spec version" and it works instantly. Another rebuilt their docs for agent visitors, saying close to 60% of their traffic is agents, and one recommends Mintlify for blogs.

7 people credit the automation instead: Autopilot reading code and systems and opening an update when something changes, Automations turning repo changes and releases into docs updates, and a docs skill that saves them fighting configs themselves.

4 people have soured. Two name money and reliability: one calls $450 a month a scam and vibe-coded their own renderer, another says a change left them "unknowingly serving totally broken pages" to users and switched off Mintlify. A third asks a company to consider migrating its docs off Mintlify, citing issues with the current ones.

Deployment trouble centres on an October 21 change: a rendering rollout moved JS and CSS assets to /_mintlify/assets, and the generic proxy guide missed the root-level /_mintlify/* route it now needs. A follow-up post confirms the change, apologises, and says the guide is being updated. Meanwhile people asked about "breaking reverse proxy deploys without notice"; one said they had been serving totally broken pages before switching off Mintlify.

On price, people quote $450 a month. Others say credits burn fast — a small edit in the editor took a large share of one person's quota — and that hitting a usage wall is when the cost gets called overpriced; one says only an enterprise upgrade will fix page speed.

The third strand is about agents reading the docs: config is where agents guess most, and one warns they invent components that don't exist. Two say drift is the real developer-experience problem.

Two more report Lighthouse scores that are "really bad" on Mintlify docs, and an audit that found duplicate h1s on all 209 pages of one site, 173 of them missing meta descriptions.

The platform-agnostic argument is put plainly: "why tie your docs workflow to a specific platform? i'd rather have an agent that works regardless of what we use for documentation," with the reply conceding it is a fair point.

The one-person themes go in different directions. One says "skills are the docs. mcp is the execution" and that there is "no more mintlify stuff." One left for an AmpCode + Slack + Linear flow where anyone can open a docs pull request from Slack or Linear and someone else verifies it. One asks whether Context7 is the option now that the Mintlify Index MCP is discontinued. One, citing $450 a month, vibe-coded their own API documentation renderer. People also name platforms used before Mintlify — ReadMe and Spotlight — and one adds that their Mintlify cost goes on the AI keeping docs current from the repo.

In the other direction, people say they came to Mintlify from GitBook and from the Google Docs-to-desktop-app switch, and one notes a docs site that moved to Holocron while another stayed on Mintlify.

The product questions are practical and open. In a thread about slow-loading docs, someone asks Mintlify directly for tips. One asks how the animations on a launch post were made. One asks whether they plan to publish a technical blog on how they built it, and one asks whether the Mintlify bot should handle a particular task.

The skill questions are the ones with detail to act on. Two people ask about custom components — whether the skill handles them or only the built-in ones, and whether custom ones need extra setup. Two ask whether it checks its own output: one wants to know if there is a build or lint step before the agent says the docs are done, and another asks for a preview build as a final step to catch invalid components, broken internal links and config errors, adding a question about whether it picks up an existing site's conventions. Two more ask how it behaves: what happens when two uploaded skills both match the task, and whether token savings came from smaller tool schemas loaded upfront or shorter results per call.

On the editor, people who use the minimal UI say they barely touch the properties panel or layers but miss moving between pages, so switching pages there "would be nice"; one of them also asks for a visual switcher.

The other wish with two people behind it is about writing the rules down once: uploading a "nitpicky style guide" so a review pass does not have to be repeated by hand, and pasting the names of projects already using Mintlify into its program page.

Several of the single asks concern the agent side. One wants the docs skill to run the local build and a broken-link check before it says it is done, because agents "write MDX fast" but miss a bad component prop or dead link until CI complains. One wants Autopilot wired into Slack and the repo so updates land where the team works. One wants the dark-plus code theme, described as perfect, available in light mode rather than the github-light default, which they say "sucks."