Grok Bot usage limit: how the weekly pool works

  1. 1
    Open ReasonOn the web, or in the Reason app for Mac.
  2. 2
    Connect GitHubChoose the repository your Bots work in.
  3. 3
    Describe the taskReason does the work and opens a pull request.

Reason sessions run on Reason's cloud and use Reason credits.

One weekly pool. Every Grok surface.

Yes, Grok Bot has a usage limit: on The X Subscription each paid seat gets one weekly pool for eligible first-party usage, shared across Grok Bot, the Grok apps and Cursor, and different activities draw different amounts from it. Your live usage view shows how much is used and the next reset date; past the pool, work continues only as paid Additional Usage from top-ups.

Check your Grok Bot weekly limit in four steps

  1. Open your usage view

    On The X Subscription, open Usage at grok.com/dashboard. In the Grok Bot app, Settings → Usage & Billing shows weekly included usage, and the account menu can show Weekly usage at a glance. On a legacy Cursor plan, check cursor.com/dashboard.

  2. Read the next reset date

    The usage view shows how much of the weekly pool is used and the next reset date. The pool resets each week. xAI's docs don't publish one reset day for everyone, so go by the date your own usage view shows.

  3. Know what draws from the pool

    Grok Bot, Grok models in the Grok apps and Grok models in Cursor all draw from the same pool; it is not split into separate product quotas. Usage rates vary by product, and xAI says how fast you use it depends on the kind of work you give Grok Bot and how much effort each task takes. Third-party models in Cursor are never in the pool: they are paid Additional Usage from the first use.

  4. Decide what happens past the pool

    After a seat uses its weekly pool, more first-party usage is Additional Usage, paid from prepaid credit you buy with top-ups. Auto Top-up is off unless you turn it on, and a monthly additional usage limit (spending cap) pauses paid usage when it is reached, even with credit left. Manage both under Additional usage credits on the billing page.

Grok Bot usage by plan

PlanList priceIncluded usageGrok Bot
Free$0LimitedNot included
Plus$8/moBaseNot included
Premium$30/mo4x PlusIncluded
Super$100/mo15x PlusIncluded
Ultra$200/mo50x PlusIncluded
Team seats$30, $100 or $200 per seatSame as the matching individual tier, per seatIncluded

Prices and multipliers are xAI's list prices on The X Subscription, before tax. xAI does not publish a number of messages or tasks per week, because different activities draw different amounts from the pool. Check x.ai/pricing for current prices and included usage before you switch plans.

Teams: seats don't share pools

On self-serve team plans, each paid seat has its own weekly pool for eligible first-party usage, and seats do not share pools. The team shares one prepaid balance for Additional Usage, and admins set one monthly additional usage limit for the whole team, as a fixed amount or per seat. Enterprise limits and controls follow the contract.

Legacy Cursor and SuperGrok plans

If you haven't switched to The X Subscription, your current billing continues. On a legacy Cursor plan, every tier includes weekly usage, higher tiers include more and Ultra the most; when the Weekly usage limit runs out, work continues as on-demand usage only if on-demand is turned on. A linked SuperGrok plan and a Cursor plan don't add together: Grok Bot uses whichever grants more.

The Weekly SuperGrok Limit in the Grok chat app is a different meter for a different product, not Grok Bot's.

Keep heavy coding work off the pool

Long coding jobs, such as reproducing a bug, running a test suite and opening a pull request, are where a Bot's effort adds up. With the Reason MCP server added, Grok Bot can start a Reason session for that work: it runs on Reason's own cloud machine and uses your Reason plan's credits, not your Grok weekly pool. Grok Bot can also message the Claude Code or Codex session on your own computer over Reason Network. Either way, Grok Bot's own messages still count.

Sources

Questions

Does Grok Bot have usage limits?

Yes. On The X Subscription, Grok Bot draws from each paid seat's weekly pool for eligible first-party usage. When the pool is used up, Grok Bot stops unless you have prepaid credit for Additional Usage, and the pool comes back at the next weekly reset.

What is the Grok Bot weekly limit?

It is the weekly pool of included usage on your plan, shared with Grok and Cursor rather than a separate Grok Bot quota. xAI states it relative to Plus: Premium includes 4x, Super 15x and Ultra 50x Plus's usage.

Is the Grok Bot limit separate from Grok and Cursor?

No. Grok Bot usage draws from the seat's shared weekly pool across Grok, Grok Bot and Cursor. It is not a separate, additive pool.

Where do I see my Grok Bot usage?

Under Usage at grok.com/dashboard on The X Subscription, or in Grok Bot under Settings → Usage & Billing. Before switching from a legacy Cursor plan, check cursor.com/dashboard.

Do top-ups make my weekly pool bigger?

No. Top-ups buy prepaid credit for Additional Usage: first-party usage past the pool, and third-party models in Cursor. The pool itself stays the same until a plan change; Super and Ultra have larger pools than Premium.

Does handing work to Reason stop Grok Bot from using my weekly pool?

No. Grok Bot's own messages, including the one where it starts a Reason session, still draw from your Grok weekly pool. The coding work itself (reading the code, running builds and tests, opening the pull request) runs in the Reason session on Reason's cloud machine and uses your Reason plan's credits instead.

Is Reason made by xAI?

No. Grok Bot is a product of xAI. Reason is built by Reason Machines and is not affiliated with or endorsed by xAI. Limits and prices on this page come from xAI's own documentation; check it for changes.

More guides