See which Bot is burning usage in Settings

How this helps you

You stop guessing which Bot emptied the weekly pool and fix the actual burner first.

Which of my Bots, requests and routines used the most of this week's usage pool? List the top offenders, what they were doing, and one change for each that would cut usage without dropping the job. Do not change anything until I approve.

What they did

During Grok Bot Q&A #1, a listener asked how to tell which requests or routines eat the most usage. Matt's first answer was to ask the Bot itself which routines fire often. Eric then opened Settings > Usage and billing, scrolled down, and toggled By bot so you can see exactly which Bots are burning tokens. They also noted the same screen shows routines. The Space chat was full of people angry about weekly limits, so this view is the practical next step before you delete Bots or buy credits: identify the heavy Bots, then audit those chats and routines.

Who it's for: Anyone mid-week on usage who still has work left.

Before you start

• Grok Bot desktop or web app
• A plan that shows Usage and billing

How to try it

1. Ask your main Bot: which requests or routines are using a lot of tokens, and is something firing too often?
2. Click your name, open Settings, then Usage and billing.
3. Scroll to the breakdown and switch to By bot. Note the top burners.
4. Check the routines list on the same screen for anything polling more than it should.
5. Open the heavy Bot's chat and trim overlapping routines or fold narrow Bots into skills before you buy top-ups.

What to expect

You get a short ranked list, then confirm in Settings > Usage and billing > By bot that the same Bots sit at the top.

Common mistakes

• Buying credits before checking By bot.
• Deleting a useful Bot when the real leak is a 10-minute poll routine.
• Ignoring the ask-your-Bot path when the Settings UI is unclear on mobile.

Related tips

• Sync two Grok Bot plans through a private fleet brain: Jordan runs two Ultra plans on one laptop and syncs bots, skills and memories through a private GitHub repo so he can switch accounts without losing context.
• Check usage and update your Bot's computer in Settings: Where to see how much of your weekly usage is left, and when to update or reset the Bot's cloud computer.
• A read-only usage audit across your whole Bot team: One prompt has your chief of staff check every Bot's routines, schedules and triggers, then report what to pause, slow, narrow or merge, and change nothing until you approve.
• Out of usage? Run these five checks before you buy credits: Grok Bot says you're out of usage but you still have credit? Check the weekly pool, the monthly cap, the meter, the account, then what's eating it.
• Build a monthly usage audit page that labels every routine: Hand your Bot screenshots of your usage and billing pages, get a page that marks each routine Keep, Slow down, Change check or Retire.

Worth knowingFrom Matt Palmer and Eric Zakariasson, Grok Bot Q&A #1 (6 Nov 2026), around 33:30. UI labels can move; if By bot is missing, rely on asking the Bot and the usage CSV tips.

Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips