Mintlify pools AI credits at the organization level, not per deployment
Mintlify now pools AI credits into one org-wide balance across all Pro deployments, replacing per-deployment tracking — an allocation change, not a price move.
Credits were tracked per deployment — each Pro-tier docs deployment had its own separate 10,000-credit monthly allotment, unshared with other deployments in the same organization.
Credits pool at the organization level. Every Pro deployment still contributes 10,000 credits/month, but every deployment and team member in the org spends from one shared balance (e.g., an org running two Pro deployments starts each month with 20,000 pooled credits).
Proof of change
Mintlify's pricing pages, as we captured them on two dates.
Showing the whole page as captured — scroll either panel, or open it at full size.
Show 1 other page we compared
Showing the whole page as captured — scroll either panel, or open it at full size.
- These prices come from our capture alone — they were not confirmed against an independent second source.
- 1 page had no counterpart in the earlier capture and is not shown.
Both images are our own captures, taken on the dates shown. The pixels are unmodified — nothing is retouched, and where a region is highlighted the marker is drawn over the image, not into it. Open either capture to see it at full resolution.
Mintlify’s own credit-pricing reference page now carries a callout stating credits “were previously tracked per deployment” and “now pool at the organization level,” alongside newly published per-action credit averages (an assistant response averages ~23 credits, an editor-agent run ~115, translations up to ~913). The headline Pro/Enterprise rate card, the $0.01/credit overage rate, and the three self-serve credit add-on tiers ($145 for 15,000, $370 for 40,000, $800 for 90,000) are unchanged — this is a metering/allocation mechanic shift, not a price move.