Topics ▾
Workflows ·

Out of usage? Run these five checks before you buy credits

Beginner, 15 minutes

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.

How this helps you

You find which limit is actually blocking you in a few minutes, instead of buying credits that may not help.

✦ Try it
I'm getting an out-of-usage message. Here are screenshots of my billing page and usage page: [screenshots]. Go through these checks in order and tell me which one is the problem: 1) is my weekly pool used up, 2) have I hit my monthly additional usage cap, 3) am I looking at the right meter (grok.com or cursor.com), 4) could my plan be on a different account, 5) what is likely using the most. Don't buy credits or change any setting.

Fill in: [screenshots]: your billing page and usage page. The video notes a Bot can't look up your usage itself, so it needs the screenshots.

What they did

Kacper Rutkiewicz kept seeing people with credit left in their account whose Bot still said they were out of usage. He opened his own billing page at grok.com/dashboard/billing to show why. It has two cards. The plan card shows the weekly included usage, which is used before any credits. The balance card has a separate line called monthly additional usage, and that line is a cap: with a $50 cap and $100 of credit, only $50 can be used this month, and buying more credit doesn't move the cap. He then walks through five checks in order: the weekly pool, the monthly cap, which meter you're on (grok.com or cursor.com), which account your plan landed on, and what is using your usage. He says he built the list from the docs and staff replies, since he's on Ultra and hasn't hit the cap himself.

Who it's for: Anyone who sees an out-of-usage message while they still have credit or weekly usage left.

Before you start

How to try it

  1. Weekly pool: on the plan card, check how much of the week is used. It resets on a rolling 7 days from when you got access, not at midnight.
  2. Monthly cap: on the balance card, find monthly additional usage. If you've hit it, click Edit and set the cap you're happy to spend. Leave auto top-up off unless you want it.
  3. Meter: if you never unified your subscription, Grok Bot is probably metered on cursor.com (Settings, usage and billing), so Grok or X credits won't unblock it.
  4. Account: if the plan landed on the wrong account, don't buy a second plan or rerun the switch. Contact support with every email you used, your devices and a screenshot of the plan Grok Bot shows.
  5. Drains: if all four look fine, find what's eating usage (long chats, frequent routines, third-party models). See the related usage audit tip.

What to expect

A short answer such as 'Your weekly pool is at 40%, but monthly additional usage shows $50 of $50 used, so the cap is what's blocking you', plus what to change.

Common mistakes

Related tips

Worth knowingCarved from a segment of this video starting at 0:42. Paraphrased by us; watch the original for the full walkthrough.
Next in Workflows →Build a weekly research briefing Bot from scratch, then test run it

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

Related Grok Bot tips

More Workflows →
Workflows

Two habits that make usage last: batch requests, send words not screenshots

Every message makes a Bot reread the chat, so send related requests together, skip 'thanks' replies, and paste text or cropped images instead of full screenshots and PDFs.

How this helps you The same work uses fewer messages and less image reading, so your weekly usage goes further without dropping any jobs.
Spotted by Sharbel A. (YouTube) · 3 Nov 2026
Workflows

Let your Bot cancel free trials and unused subscriptions

Three built-in templates from 0.78: start a trial and cancel it before it bills, cancel plans you don't use, and watch renewal prices.

How this helps you You stop paying for trials and plans you forgot about, and nothing is cancelled without your OK.
Spotted by @spectnfa · 31 Oct 2026
Workflows

From support form to fix: a webhook, a Bot and a Cursor cloud agent

A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.

How this helps you By the time an engineer looks at a bug, it has repro steps, a test and a proposed fix waiting.
Spotted by Grok, Santi Garza (YouTube) · 29 Oct 2026