Credit pricing

Mintlify’s AI features run on credits. 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. Two things stay with the individual deployment: its plan, and its overage setting, which decides whether that deployment keeps running after the shared balance runs out.

​

What uses credits

Three products draw from your balance: the assistant, the agent, and automations. Automations consume credits each time they run, whether you run them on a schedule, on a trigger, or manually. These numbers are averages. A single run costs more or less depending on the size of the task: how much content the agent reads, how many files it changes, and how long the run takes.

​

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.

​

Credit add-ons

Each add-on adds credits to your organization’s monthly balance on top of what your plans include. 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 works out to about 8% less per credit than the 15,000-credit one, and all three 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 we prorate 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.

​

Estimating your usage

Use the averages in What uses credits to estimate what your organization needs each month. A site that handles 500 assistant responses per month uses roughly 11,500 credits (500 × 23). Adding a weekly broken link detection automation adds about 1,140 credits per month (4 × 285). Estimates get you to a starting point. After a month of real usage, check the Usage page and adjust your add-on.

​

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 lowers credit consumption because the agent batches work across multiple changes in a single run. 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 costs more than you expect, review its trigger frequency and any custom instructions that widen its scope.