Fixes / Cost

How to limit Grok Bot spending

How to control Grok Bot spending when there is no separate per-Bot cap. Set the account limit, add alerts, bound every routine and test the stop procedure.

Short answerGrok Bot does not currently have a separate spending cap for each Bot. If you are testing it for the first time, turn off on-demand usage at the account level. Then add usage alerts, give every routine a fixed schedule and stop condition, and test how to pause it before leaving it unattended.

Start here if this is your first Bot

  1. Open the account billing or usage dashboard.
  2. Find the account-level on-demand usage control.
  3. Turn on-demand usage off while you test your first workflow.
  4. Run that workflow manually with one small input.
  5. Check the billing dashboard after the run. Use the dashboard as the billing record, even if the Grok Bot app shows a different percentage.

This prevents usage beyond the included allowance during testing. It does not create a separate budget for each Bot.

The four controls you need

Control What to set What it prevents
Account limit Disable on-demand usage, or set only the amount the owner has approved. Account usage continuing beyond the approved budget.
Usage alerts Check daily and alert at 60% and 85%. Finding out about rising usage after the billing period.
Routine limit Set the schedule, allowed source, maximum records and stop condition. A routine checking forever or rereading the same work.
Emergency stop Name the person who can pause routines and revoke access. Confusion while spend is already rising.

Fix every unbounded routine

Open each routine and answer these questions in the instruction:

  1. When does it run?
  2. Which records may it read?
  3. How many records may it process in one run?
  4. What counts as new work?
  5. When must it stop?
  6. Who receives an alert if the result is unusual?

Replace instructions such as "keep checking for updates" with a fixed schedule. Replace "review all records" with a date range, changed-record filter or maximum count.

Copy this usage-watcher instruction

Daily at 07:00, read the account usage dashboard. Append the date, allowance percentage and on-demand spend to ops/spend-log.csv. Alert the owner at 60% and again at 85%, or after any unexpected day-over-day increase. Name the routines with the most runs. Take no other action. Stop.

The watcher reports usage. It should not pause other routines by itself.

Test the stop procedure

Before the first unattended run:

  1. Start a low-risk routine with a small input.
  2. Pause it while it is active.
  3. Confirm that the next scheduled run does not start.
  4. Confirm that the Bot can no longer use any connector you revoked.
  5. Write down who performed the stop and where the account limit is managed.

If spending has already jumped

  1. Pause the routine with the most recent or frequent runs.
  2. Check its run history for repeated reads, hourly schedules, delegation loops and missing stop conditions.
  3. Keep on-demand usage off until you know which instruction caused the increase.
  4. Fix and test that routine with one input before turning the schedule back on.

Do not create another routine to diagnose or pause the first one while the cause is unknown.

What number should you choose?

There is no safe universal amount. Start with on-demand usage disabled. If the business later enables it, the owner should choose the amount and record that decision. The routine limits above still matter because the account control is shared by every Bot.

Runaway routine · Usage meter mismatch · Grok Bot pricing explained

Related

Reviewed 1 Sep 2026 · How we review guides · See changelog.