Mintlify Autopilot
Mintlify · Mintlify Autopilot: Always-On Agent That Opens Docs Pull Requests When Your Code Changes
Mintlify Autopilot is a background agent for docs hosted on Mintlify that reads merged code changes and the context around them, drafts documentation updates, and opens pull requests for a teammate to review. It suits developer-facing companies already on Mintlify Pro or Enterprise whose docs fall behind what engineering ships.
Best for
Developer-facing companies already hosting docs on Mintlify Pro or Enterprise, with code in GitHub, whose engineers ship faster than the docs team can follow and who want every doc change to arrive as a reviewable PR
Not ideal for
Teams whose docs live outside Mintlify, GitLab or Bitbucket shops, small projects that cannot justify Pro pricing, and teams that need production-grade tooling rather than a beta
Who it's for
Docs, developer relations, and engineering teams at software companies that host their documentation on Mintlify and keep code in GitHub
Capabilities
- Runs in the background after a single dashboard toggle, deciding on its own which pages need updating instead of following per-workflow prompts
- Reads merged code changes in connected GitHub repositories and drafts the matching documentation updates
- Runs a once-daily quality check by default, and takes extra recurring jobs you ask for in chat, such as a weekly broken-link check
- Commits to a new branch and opens a pull request, targeting your deploy branch by default; it never pushes to the deploy or default branch
- Assigns each PR to the teammate it identifies as the owner of the changed code, requests their review, and emails them from autopilot@mintlify.com
- Dashboard Suggestions view with changed files, line counts, preview deployment links, and Accept, Close, or ask-for-changes actions
- Configured by chatting with it: ask why it opened a PR, change reviewers, retarget a branch, or pause and resume a kind of work
- Builds context from your docs, extra source repositories, Slack, and (on Enterprise) shared integrations such as Linear, Jira, Notion, Confluence, Zendesk, Intercom, Plain, Pylon, and PostHog
- Checks which Mintlify automations are active and avoids duplicating their work
- Pauses itself when credits run out or the plan no longer includes it
Limitations
- Only maintains documentation hosted on Mintlify, so teams on other docs platforms have to migrate first
- Requires a Mintlify project connected to GitHub with the Mintlify GitHub App installed; Autopilot does not support GitLab or other Git providers, even though Mintlify automations do
- Needs a Pro ($450 a month billed annually, $540 monthly) or Enterprise plan; the free Starter plan has no AI features
- On Pro, Autopilot connects only GitHub and Slack; project trackers, support tools, and feature-flag sources require Enterprise
- Each run that opens or updates a PR costs 250 credits from a balance shared with the assistant, automations, and narration, and overages cost $0.01 per credit ($2.50 per PR)
- Still in beta; learning from reviewers' edits before merge and an activity dashboard are listed as next steps rather than shipped
- Changes that happen while Autopilot is paused are added to its context but do not get doc updates when it resumes
- Chatting with Autopilot requires the editor or admin role, and merge conflicts or blocked merges must be resolved on GitHub
Use cases
- Getting a docs PR drafted automatically when an engineer merges a new CLI flag or API parameter
- Turning a recurring support question into a documentation page that the agent keeps current (support tools connect on Enterprise)
- Picking up a Slack thread where someone flags that the docs are wrong and opening a fix
- Running scheduled maintenance such as a weekly broken-link check without writing an automation
- Replacing a set of hand-tuned Mintlify automations with one agent while keeping translation automations
Our take
Autopilot is worth turning on for teams already paying for Mintlify Pro, because the cost only shows up when it produces a PR and every change still goes through review. Ten thousand monthly credits cover about 40 Autopilot PRs, but the same balance also pays for assistant answers, so busy docs sites should watch usage before relying on it for every merge. It is not a reason on its own to move to Mintlify: it only maintains Mintlify-hosted docs, it supports GitHub only, and support-ticket, project-tracker, and feature-flag context beyond GitHub and Slack needs Enterprise. Treat it as a beta that drafts and routes updates to the right reviewer, not as a replacement for a docs owner.
Who should use it
Mintlify Pro and Enterprise customers with code in GitHub who want doc updates drafted as soon as features merge, docs and DevRel teams who currently chase engineers for changes, and teams that have built several automations and would rather manage one agent.
Who should skip it
Teams on other docs platforms who do not plan to migrate, GitLab or Bitbucket users, open source or small projects that cannot justify Pro pricing (unless they qualify for Mintlify's OSS or startup programs), and teams that need help-center tooling for end-user support content.
Strengths
- No prompts or triggers to configure: switch it on and it decides what to update
- Every change arrives as a pull request with an owner assigned, never a direct push
- Outcome-based pricing: runs that change nothing cost nothing
- Steered in plain-language chat, and it learns from PRs your team merges or closes
- Uses Slack and, on Enterprise, support, tracker, and feature-flag context, not just code diffs
Weaknesses
- Only works for docs hosted on Mintlify
- GitHub only; no GitLab support
- Requires Pro at $450 a month or more
- Sources beyond GitHub and Slack need Enterprise
- Still in beta
Mintlify Autopilot pricing
Pro
$450 (annual) or $540 (monthly)
Billed monthly
- Autopilot in beta
- 10,000 credits per month shared across AI features
- 250 credits per Autopilot PR opened or updated; free when nothing changes
- Autopilot sources: GitHub and Slack
- Unlimited editor seats, editor and Slack agent, automations, preview deployments
Enterprise
Custom
- Autopilot in beta
- Custom credits with committed volume discounts
- Shared integrations as Autopilot context (Linear, Jira, Notion, Confluence, Zendesk, Intercom, and more)
- SSO, SCIM, RBAC, and audit logs
Free tier limits: The free Starter plan does not include Autopilot or any AI features. New accounts get a 14-day Pro trial with 5,000 credits and no card required, which Mintlify's launch post points new users to for trying Autopilot; the trial ends after 14 days or when the credits run out.
Note: Each Autopilot run that opens or updates a pull request costs 250 credits, however many pages it changes; runs with nothing to update cost nothing. Credits pool across the organization and are shared with assistant answers (25 credits), automations (250), and narration (50). Overages are off by default and cost $0.01 per credit. Add-ons: 15,000 credits for $145, 40,000 for $370, or 90,000 for $800 a month. Up to 50% of unused credits roll over.
Technical specs
Modalities
text
Where Mintlify Autopilot excels
Documenting features as they merge
When an engineer merges a change such as a new CLI flag, Autopilot reads the diff, drafts the doc update, and emails the code owner a PR to review, so the docs change is waiting before release instead of weeks later.
Closing gaps that support keeps hitting
With Slack connected, and on Enterprise a support tool such as Zendesk or Intercom, Autopilot can write and maintain a page for a question that keeps coming in, or pick up a Slack thread flagging an outdated page and open the fix.
Consolidating docs maintenance automations
Teams running several prompt-based automations can switch most of them off and let Autopilot decide what to update, keeping translations as an automation, which reduces prompt upkeep.
Mintlify Autopilot vs. competitors
Mintlify Autopilot vs. Ferndesk
Ferndesk is a hosted help center whose agent, Fern, verifies end-user articles against your code, live product, and support tickets and drafts fixes from merged PRs. Mintlify Autopilot maintains developer documentation in a Git repository and delivers changes as GitHub pull requests rather than in-app drafts. Both only maintain docs hosted on their own platform, so the choice usually follows whether your docs are a customer help center or a developer docs site.
Frequently asked questions
What is Mintlify Autopilot?
Autopilot is a background agent in the Mintlify documentation platform. It reads your docs, connected GitHub repositories, and other connected sources, drafts documentation updates when something changes, and opens pull requests for your team to review. It launched in beta on October 20, 2026.
How much does Mintlify Autopilot cost?
Autopilot requires a Mintlify Pro or Enterprise plan. Pro is $450 a month billed annually or $540 billed monthly and includes 10,000 credits a month shared across AI features. Each Autopilot run that opens or updates a pull request costs 250 credits, and runs that find nothing to update are free. Extra credits cost $0.01 each as overages, or come in add-ons of 15,000 ($145), 40,000 ($370), or 90,000 ($800) credits a month. Enterprise credits are custom.
Does Autopilot publish changes on its own?
No. Autopilot commits to a new branch and opens a pull request, tags the teammate who owns the changed code, and emails them. It never pushes to your deploy branch or default branch, so nothing ships until someone merges.
Can I try Mintlify Autopilot for free?
Not on the free Starter plan, which has no AI features. Mintlify's launch post points new users to the 14-day Pro trial, which needs no card and includes 5,000 credits, enough for up to 20 Autopilot pull requests if nothing else uses them. The trial ends after 14 days or when the credits run out, whichever comes first.
Does Mintlify Autopilot work with GitLab?
No. Autopilot needs a Mintlify project connected to GitHub, with the Mintlify GitHub App installed on the docs repository and any source repositories it should read. Mintlify's automations support GitLab, but Autopilot does not.
What sources can Autopilot use?
Your docs repository is always included, and you can add source code repositories where the Mintlify GitHub App is installed. On Pro, Autopilot connects GitHub and Slack. Enterprise can also connect shared integrations such as Linear, Jira, Notion, Confluence, Zendesk, Intercom, Plain, Pylon, and PostHog.
Mintlify Autopilot vs automations: what is the difference?
With automations you choose a trigger and write and maintain a prompt for each workflow, and each run that updates docs costs 250 credits. Autopilot needs no prompts or triggers: it decides what to change, avoids duplicating active automations, and learns from your reviews. Mintlify recommends keeping translation automations and letting Autopilot take over most other maintenance.
Integrations & fit
About Mintlify Autopilot
Autopilot is the hands-off layer on top of Mintlify's docs agent. Mintlify already offered the agent in its web editor and Slack, plus automations, where you pick a trigger and write and maintain a prompt for each recurring job. Autopilot drops that setup: you switch it on, point it at your docs repository and any source code repositories with the Mintlify GitHub App installed, and it decides what to change. By default it proposes updates when code changes and runs a once-daily quality check; Mintlify's launch post also describes it writing pages for support questions that keep coming up and acting on Slack threads that flag a mismatch. Every change lands on a new branch as a pull request, by default against your deploy branch. Autopilot never pushes to the deploy or default branch, assigns the PR to the teammate it identifies as the owner of the changed code, and emails them. Suggestions also appear in the dashboard, where you can preview, accept (merge), close, or ask for changes. There are no prompts to manage: you steer it in chat (who reviews, which branch to target, extra jobs such as a weekly broken-link check), and Mintlify says it learns tone and update cadence from the PRs your team merges or closes. It is in beta on Pro and Enterprise. On Pro, GitHub and Slack are the connected sources; Enterprise adds shared integrations such as Linear, Jira, Notion, Confluence, Zendesk, Intercom, Plain, Pylon, and PostHog. Pricing is outcome-based: each run that opens or updates a PR costs 250 credits from the organization's shared balance, and runs that change nothing are free. Pro is $450 a month billed annually ($540 monthly) with 10,000 credits a month, enough for 40 Autopilot PRs if nothing else draws on them. The main tradeoffs are that it only maintains docs hosted on Mintlify, it supports GitHub only (no GitLab), richer context sources need Enterprise, and it is still a beta.
Updates from Mintlify Autopilot
Mintlify released Autopilot, an always-on agent that drafts documentation updates from code merges, support questions, and Slack threads and opens pull requests for review. It is in beta on Pro and Enterprise plans, and each PR it opens or updates costs 250 credits.
Are you the founder? Claim this listing →