Clarify that overages have no spending limit

[MTSUBOOR]

Documentation changes

A customer (and me, in advising them) was mislead by this page's claim that you can set an overage limit. While the backend code has an option set up for this, our UI does not expose it. So, for all intents and purposes, we don't offer this.

---

For Reviewers

When reviewing documentation PRs, please consider:

✅ Technical accuracy

• Code examples work as written
• Commands and configurations are correct
• Links resolve to the right destinations
• Prerequisites and requirements are accurate

✅ Clarity and completeness

• Instructions are clear and easy to follow
• Steps are in logical order
• Nothing important is missing
• Examples help illustrate the concepts
• Content follows the style guide

✅ User experience

• A new user could follow these docs successfully
• Common gotchas or edge cases are addressed
• Error messages or troubleshooting guidance is helpful

---

Note

Low Risk
Documentation-only wording change with no product or code impact.

Overview
Updates the Allow overages section in assistant/configure.mdx so it matches what the dashboard actually offers.

The doc no longer says customers can set different overage limits per project. It now states overages are on or off per project, that overages have no spending cap, and points readers to usage alerts for monitoring spend.

^{Reviewed by Cursor Bugbot for commit 16553a9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
mintlify	🟢 Ready	View Preview	Sep 29, 2026, 2:57 AM

[MTSUBOOR]

@ethanpalm I (and my clanker) were not sure about how we handle translation. Should I just edit the English version, and assume an automation will handle downstream translation, or should I edit the Chinese, French, and Spanish versions?