Token Cap Needed for "AI-powered Summary on Search Pages"

I need to flag a serious issue with the Enable AI-powered summary on search pages feature, and request that a token cap or rate limiting control be added.

What happened

I enabled this feature on our directory and within a single day we had consumed 63 million tokens. One day. That is not a typo.

At OpenAI pricing, 63 million tokens at $5.00/M input and $30.00/M output represents a potentially catastrophic unplanned cost for any directory operator. Even at budget provider rates this is deeply problematic at scale.

Why this feature is uniquely dangerous compared to the others

Every other AI toggle in the Configure AI Integrations panel is bounded by human interaction:

AI suggest for admins and sponsors — fires only when a human edits content
AI review summaries — fires per listing, capped by listing count
AI content moderation — fires on submission events only
AI mode on search bar — interprets a query but does not generate a full page summary

The AI-powered summary on search pages is different. It fires automatically on every single search page load with no ceiling. Directory sites attract significant automated traffic — bots, crawlers, indexing spiders — and every one of those hits to a search URL burns tokens silently in the background with no warning and no limit.

This is not a configuration issue on our end. It is a missing guardrail in the platform.

What I are requesting

Please add the following controls specifically for this feature:

Daily token cap — hard ceiling after which the feature simply does not fire for the remainder of the day
Monthly token cap — a broader budget limit with an alert when approaching the threshold
Email alert — notify the admin when token usage crosses a configurable threshold (e.g. 50%, 80%, 100% of cap)
Bot/crawler exclusion — option to suppress AI summary generation for non-human traffic
Rate limit per IP or per session — prevent any single visitor or bot from triggering unlimited AI calls in a short window

Any one of these would have prevented our 63 million token day. All five together would make this feature genuinely safe to run in production.

Until one or more of these controls exist, toggled it off.

Thanks,
Aaron