Skip to main content
Some Mintlify features consume credits.
  • Assistant responses
  • Agent runs in the editor or on Slack
  • Automation runs
For the most current pricing information, see the Pricing page or view the Usage page in your dashboard.

​
Pricing tiers

If you need more than 108,500 credits per month, contact sales to discuss a custom plan. Overages cost an additional $0.01 per credit rather than triggering an automatic tier upgrade. You can set usage alerts to receive an email when you reach a certain percentage of your tier limit. Allowing overages can be cheaper than moving up a tier depending on your usage patterns.
Overages default to off. You must enable them on the Usage page of your dashboard.
Rollovers carry forward up to 50% of unused credits to the next month, so the maximum credits available in any month is 1.5 times your monthly limit. Rollovers reset if you change tiers. Higher tiers offer a lower effective cost per credit. If your usage consistently reaches the top of your current tier, upgrading is more economical than paying ongoing overage charges. Upgrades and downgrades take effect immediately, and we prorate the charges to the current billing cycle. For high-volume usage or custom credit packages, contact sales. Custom credit packages are available on enterprise plans only.

​
How credits work

Different features consume different amounts of credits per interaction: Automations also consume credits when they run:

​
Estimating your usage

Use the averages in the How credits work section to estimate your monthly credit needs. For example, if your docs site handles 500 assistant responses per month, that’s roughly 11,500 credits (500 × 23). Adding a weekly broken link detection automation adds about 1,140 credits per month (4 × 285). After using credit-powered features for a month, review your usage patterns to see if you should adjust your tier.

​
Cost optimization

Schedule automations instead of triggering on every push. Automations like SEO audits, writing style checks, and broken link detection don’t need to run on every code change. Running these on a daily or weekly cron schedule rather than on every push significantly reduces credit consumption without meaningful impact on content quality. Monitor your usage patterns. The Usage page in your dashboard shows a breakdown by feature category. If a particular automation is consuming more credits than expected, review its trigger or any custom instructions.