Credit pricing

Learn the fixed credit price of each AI action, how your shared credit balance works, and how Mintlify bills add-ons, overages, and rollovers.

Mintlify’s AI features run on credits. Every action has a fixed credit price, and you pay only when an action produces a result. Your organization has one monthly credit balance, shared by every deployment and everyone on your team. Manage it on the Usage page in your dashboard.

Your shared balance

Your balance comes from three places:

• Your plans. Every Pro plan in your organization contributes 10,000 credits per month. An organization with two Pro deployments starts each month with 20,000 credits.
• Add-ons. Buy an add-on when you need more than your plans include. An add-on is one purchase for the organization rather than one per deployment, and any deployment can spend it.
• Rollover. Unused credits carry into the next month and join the same balance.

Every deployment and every team member spends from that shared balance. The Usage page shows the organization-wide balance, with per-deployment usage broken out below it.

Individual deployments have their own overage settings, so you can configure different overage behaviors for each one.

Credits were previously tracked per deployment. They now pool at the organization level.

What uses credits

Every AI action has a fixed credit price. Actions that produce nothing cost nothing.

Action	Credits
Assistant answers a question	25
Assistant can’t answer a question	0
Automation updates your docs	250
Automation finds nothing to update	0

The price is the same regardless of how much content the agent reads, how many passes it takes, or how long the action runs.

Using the agent in the editor or Slack does not consume credits.

Assistant answers

An answer is a response that addresses the user’s question. Each answer costs 25 credits, whether the question comes from your docs site, the widget, or the assistant API.

If the assistant can’t find an answer in your docs and says so, the message costs nothing.

Automation updates

An update is a run that changes your docs, either by opening or updating a pull request or by committing directly to your repository, depending on the automation’s update mode. Each update costs 250 credits, whether the run starts on a schedule, on a trigger, manually, or through the API. A run that changes several pages is still one update.

A run that reviews your repository and finds nothing to update costs nothing. Runs that fail also cost nothing.

Editor agent and Slack agent

Pro and Enterprise plans include the editor agent and the agent in Slack. Using them doesn’t consume credits.

Before September 8, 2026, credit costs varied with the tokens each run used. Fixed prices apply automatically to every action from that date. Your plan, its included credits, and the price per credit stay the same.

Plan availability

Credits are available on the Pro and Enterprise plans.

The Starter plan does not include AI features, and you cannot purchase credits on it. To use the assistant, agent, or automations, upgrade to Pro or Enterprise.

Customers on legacy credit plans keep their existing credit packs and pricing. The add-ons below apply to the Pro plan.

Credit add-ons

Each add-on adds credits to your organization’s monthly balance on top of what your plans include.

Extra credits per month	Monthly cost
15,000	$145
40,000	$370
90,000	$800

A single Pro deployment with the 40,000-credit add-on has 50,000 credits per month. Larger add-ons cost less per credit. The 90,000-credit add-on costs about 8% less per credit than the 15,000-credit one. All three add-ons cost less per credit than the $0.01 overage rate.

Add or change an add-on in the Credit packages section of the Usage page. Changes take effect immediately, and Mintlify prorates the charges to your current billing cycle.

The 90,000-credit add-on is the largest you can buy yourself. For more than that, contact sales to discuss a custom credit package, available on Enterprise plans only.

For the most current pricing, see the pricing page.

Spending controls

Overages

Overages let a deployment keep running after your organization exhausts its monthly credits, at $0.01 per additional credit. They are off by default. Enable them in the Spending controls section of the Usage page.

You configure overages per deployment, so when the shared balance runs out, each deployment’s own setting decides what happens to it. A deployment with overages off loses its credit-powered features until the balance resets.

Every add-on costs less per credit than the $0.01 overage rate. Use overages to absorb an occasional busy month. If your organization exceeds its balance consistently, buy an add-on or move to a larger one instead.

Usage alerts

Set usage alerts in the Spending controls section of the Usage page to receive an email when your organization reaches a given percentage of its balance. Alerts cover the organization as a whole rather than a single deployment.

Rollovers

Up to 50% of unused credits carry forward to the next month, so the most your organization can have available in any month is 1.5 times its monthly balance. Rollovers reset when you change add-ons.

Estimate your usage

Because every action has a fixed price, you can project usage from volume alone:

• Multiply the number of questions you expect the assistant to answer each month by 25.
• Multiply the number of automation runs you expect to update your docs each month by 250.

For example, an organization whose assistant answers 200 questions and whose automations make 12 updates in a month uses 8,000 credits, which fits within a single Pro plan’s 10,000 monthly credits.

The Activity log section of the Usage page lists each action and the credits it consumed, so you can check your projection against real usage.

Export usage activity

Export your usage activity log to CSV for deeper analysis, reporting, or record-keeping.

1. Navigate to the Usage page in your dashboard.
2. Optionally, adjust the date range in the toolbar to change the period the export covers.
3. In the Activity log section, click Export to CSV.
4. Mintlify emails you a download link when the export is ready. The link expires after 72 hours.

The exported CSV includes the date, product, and credits consumed for each event in the selected range.

Reduce credit usage

Run automations on a schedule

SEO audits, writing style checks, and broken link detection don’t need to run on every code change. A daily or weekly schedule batches multiple changes into a single update, so you pay 250 credits once instead of once per change. Runs that find nothing to update are free, so a schedule that runs more often than your content changes doesn’t cost extra. The tradeoff is a delay between when content changes and when the automation acts on it.

Find what’s consuming your credits

The Usage page breaks usage down by feature category. If one automation makes more updates than you expect, review its trigger frequency and any custom instructions that widen its scope.