Support bots

Stop a busy support week from emptying the provider account.

The bot keeps answering until the ceiling you set. The next request after that is a 402, and the provider is not called.

What goes wrong without a ceiling.

The provider bill arrives after the traffic. Fuse is the stop in front of that call.

01

A ticket spike can spend more in a day than the bot spent all last month.

02

The provider dashboard shows the bill after the fact. Fuse stops the next call.

03

A warning email fires at the percent you pick, before the hard stop.

On this project

Three ways to cap a support bot.

Play 1

One project for the bot

Store the provider key the bot uses. Turn on only the models it is allowed to call.

Monthly $25 · warn at 80% · Europe/Budapest
Play 2

Warn, then block

Set the warning at 80%. The first request that would cross the limit returns 402.

402 · fuse_blown · provider not called
Play 3

Keep the transcript out

The log shows model, tokens, and cost. The customer message is not stored.

14:02 · gemini-2.5-flash · $0.002 · 200

All use cases