diff --git a/credits.mdx b/credits.mdx index 9a61341a2..1bc02b0ad 100644 --- a/credits.mdx +++ b/credits.mdx @@ -52,7 +52,7 @@ A run that reviews your repository and finds nothing to update costs nothing. Ru Pro and Enterprise plans include the [editor agent](/editor/agent) and the [agent in Slack](/agent/slack). Using them doesn't consume credits. - Before September 4, 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. + 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 @@ -129,10 +129,6 @@ The exported CSV includes the date, product, and credits consumed for each event 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. -### Bring your own model - -On Enterprise plans, you can supply your own LLM provider API key and choose the model behind the assistant, agent, and automations. Mintlify meters usage at a reduced credit rate, and your provider bills you directly for inference. You configure models per deployment, not for an entire organization. See [Bring your own model](/ai/bring-your-own-model) for more information. - ### Find what's consuming your credits The [Usage](https://app.mintlify.com/settings/organization/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.