# Stop one job eating your bot usage

> Tested by AI Setups That Work. Small business · Intermediate · Operations. Updated 2026-11-16.
> Receipt: Ran on Grok Bot, Nov 2, 2026: the real 7-day usage report (14 routines, 7 bots) got a keep, trim, merge or retire call per routine and a top-3 list. Bot-to-bot messages (about 40%) cost more than the routines (about 16%); chats with the owner were 44%. Nothing was changed.

Canonical page: https://www.aisetupsthatwork.com/setups/find-which-bot-routine-burns-your-usage/

## What it does
Find the one bot, chat or routine using most of your weekly usage, then trim, merge or pause it, with a spend cap so nothing burns silently.

## Who it's for
Owners running several bots whose plan runs out early and who cannot tell which routine is to blame.

## Tools
- Grok Bot or your agent tool
- Your usage page or export
- A simple routine list

## Steps
1. List every scheduled routine and bot: what it does, how often it runs, and when you last used its output.
2. Mark the usual heavy hitters: anything that clicks through websites, retries on failure, runs every few minutes, or loads long instructions every time.
3. Run the prompt below on your list and usage export.
4. Act on the calls: retire what nobody used, merge duplicates, slow down frequent runs, swap browser clicking for a connector or export.
5. Set caps and approvals for spend. xAI documents spend and purchase approvals for Grok Bot; for API keys, set a monthly limit per key.
6. Repeat the review monthly. Grok Bot group owners reported plans used up within an hour; a monthly review catches the routine before it does that.

## Copy-paste prompt
Adapt bracketed fields to your situation.
```text
Here is my list of bot routines and my usage data. Use only what I paste.

Routines (name, what it does, how often, last time I used its output): [PASTE]
Usage export or notes: [PASTE]

For each routine:
1. Likely usage: high, medium or low, with the reason (browser clicking, retries, frequency, long instructions)
2. Call: KEEP, TRIM (how), MERGE (with what) or RETIRE
3. A cheaper way to do the same job, if one exists, such as a connector, an export or a less frequent schedule
Then list the top 3 changes that would save the most. Do not change any bot; this is a proposal for me to approve.
```

## Guardrails
- What it touches: Connected mail, calendar, sheets, or chat. Scoped to this job (Grok Bot or your agent tool; Your usage page or export).
- Needs your OK: Send, pay, publish, and account changes stay with you. Treat agent output as drafts first.
- Safety level: Read-only
- What the Grok Bot docs say about routines and usage: Each routine run spends usage, so a routine that runs often spends more than one that runs rarely. The docs warn that an hourly schedule, a short interval or a Slack trigger on a busy channel can use a week of usage in a day. Their order of fixes: pause routines you don't need, then ask the Bot to widen schedules and narrow Slack triggers, and only then raise your plan or on-demand limit. Pressing Test on a routine also spends usage, because it does the work.
- Where to look in the app: Click the Bot's name at the top of its chat to open its details. Routines are on the Details tab, each with its schedule or Paused and a switch to pause it. On the phone, open the Bot's profile, then Routines, then a routine to see Next run and Run history (Running, Succeeded or Failed).
- Cutting the routine people rely on because it looks expensive.
- No list of routines, so nothing to review.
- Letting a bot rewrite other bots instead of proposing changes.

## Tips
- Outputs nobody reads are the easiest savings.
- Browser clicking is usually the most expensive way to do a job.
- Tag runs by task or client if you bill clients for bot work.

## Estimates (labeled, not measured)
- Time saved: About 30 minutes a month.
- Money saved: Not stated in sources.
- Tool cost: Prices: Not stated in sources.

## Sources
Summaries use the public sources below, not independent verification.
- xAI: https://docs.x.ai/grok-bot/approvals-security-and-privacy (Grok Bot approvals, security and privacy: approvals for sends, spend and purchases; shared computer, local execution settings and connector hygiene (as cited elsewhere in this catalog))
- Anthropic: https://platform.claude.com/docs/en/api/rate-limits (Rate limits: set your own monthly spend limit below your tier cap on the Billing page in the Claude Console; requests stop when it is reached (read 2026-11-02 from a search result excerpt of the page))
- xAI: https://docs.x.ai/grok-bot/skills-routines-and-automations#routines-and-usage (Skills and routines, Routines and usage and Manage routines sections (read Nov 9, 2026): each run spends usage; hourly schedules, short intervals or busy Slack triggers can use a week of usage in a day; pause, widen schedules and narrow triggers before raising limits; Test spends usage.)
- xAI: https://docs.x.ai/grok-bot/faq#how-do-i-stop-charges-after-my-weekly-usage-runs-out (Grok Bot FAQ (read Nov 9, 2026): where to set Auto Top-up, the monthly additional usage limit and the on-demand monthly limit; the cap does not stop a Bot mid-run.)

## Get the free starter pack
Five beginner copy-paste AI setups, free by email: https://www.aisetupsthatwork.com/starter-pack/?utm_source=ai-agent&utm_medium=markdown&utm_campaign=setup-find-which-bot-routine-burns-your-usage

Related:
- [Cap what your AI agent can spend](https://www.aisetupsthatwork.com/setups/cap-what-your-ai-agent-can-spend/index.md)
- [Rate your bot fleet and forecast usage](https://www.aisetupsthatwork.com/setups/rate-bot-fleet-and-forecast-usage-with-mission-control/index.md)
- [How to use OpenRouter free models to stretch your AI bot's usage](https://www.aisetupsthatwork.com/setups/openrouter-free-models-stretch-ai-bot-usage/index.md)
