Grok Bot Usage Limits: How the Weekly Pool Works
Grok Bot runs on 2 different meters depending on your plan family. How the weekly pool and the legacy grant work, and what happens when you run out.
Last Updated: November 2026
Grok Bot usage limits are the weekly allowances governing how much work the agents can do. They run on two different meters, depending on your plan family. On The X Subscription, usage draws from a single shared weekly pool that also covers Cursor and the Grok apps. On a legacy Cursor plan, the agent has a separate weekly grant of its own that nothing else touches.
AiBuildrs builds custom AI systems for mid-market businesses. The team has completed over 200 successful AI implementations, producing $4.7M in documented client cost savings. Builds run to a 45-day average timeline from Strategy Day to a live system.
The distinction is not cosmetic. Both models refresh on the same weekly cadence. But they overflow in completely different ways, and they are billed through different routes. Teams that assume one model covers both end up buying capacity twice.
Key Takeaways
- Two meters, not one: The X Subscription uses a shared weekly pool. Legacy Cursor plans use a separate weekly grant. Both reset weekly, but they are not the same mechanism.
- Overflow works differently: The shared pool overflows into prepaid credit. The legacy grant overflows into on-demand billing, and only if you have enabled it.
- Metering lives on the Cursor account: Your usage figure sits in Cursor, not in Grok or X. That is where you check what is left.
- Linking raises, it does not stack: A linked SuperGrok or Grok Business seat gives you the higher of the two weekly allowances, never the sum.
- Apple platforms share one bucket: macOS and iOS draw from the same allowance rather than from separate ones.
- No published numbers: Neither vendor publishes the size of any pool or grant. Treat any article quoting a figure as unverified.
Those six points describe the two meters and what they share. The sections below cover which plans include the agent and how each meter behaves under load. Then what happens when an allowance runs out, and what switching costs you.
Which plans include Grok Bot usage?
Grok Bot is included on the Premium, Super and Ultra tiers of The X Subscription. The Free and Plus tiers do not include it. No usage allowance exists on those accounts at all.
On the legacy side the coverage is broader. Every paid individual Cursor plan includes the agent, meaning Pro, Pro+ and Ultra. Cursor Teams includes it as well, and there is no free legacy route either.
Larger organisations sit outside both arrangements. Cursor Enterprise access is enabled through an account executive. Grok Enterprise goes through an account manager instead.
One point confuses almost everyone reading the tier lists. Ultra is not a single thing. It exists as a legacy Cursor plan and as an X Subscription tier, and the two carry different usage mechanics despite the shared name.
Check which family your Ultra belongs to before reasoning about your limits. There is also no standalone Grok Bot subscription, so the allowance always arrives attached to a wider plan.
How is usage metered on each plan family?
On The X Subscription, Grok Bot draws from one shared weekly pool. According to xAI's documentation (2026), Cursor and the Grok apps draw from that same pool. The three compete for one allowance that refreshes weekly.
This has a practical consequence worth planning around. A heavy week in the Grok apps reduces what remains for the agent. The capacity is pooled rather than ringfenced per product, which teams used to per-tool budgets find surprising.
Legacy Cursor plans work the other way. Cursor's help pages (2026) describe a weekly grant attached to the plan. Pro is weekly usage, Pro+ is higher, and Ultra is the highest legacy grant. That grant is not shared with anything else.
Both models meter on the Cursor account. Your Grok account and your X account do not show the figure, which sends people looking in the wrong place. On Apple platforms, macOS and iOS draw from one shared bucket.
Neither vendor publishes the actual size of a pool or a grant. AiBuildrs checks which meter applies before sizing any agent workload for a client, because the two behave differently under load.
Rivals publish even less. Meta has released no usage limits and no pricing for Muse, and Meta's own write-up (2026) describes the product without quantifying any allowance. Anthropic has not published limits for Claude Duet, which remains a research preview.
What happens when you hit your weekly limit?
On The X Subscription, an empty pool does not stop the work. Additional usage is paid for from prepaid credit, which you load onto the account as top-ups in advance.
This is a prepaid model, not a post-paid one. If no credit is loaded when the pool empties, usage stops until you add some. Nothing is billed to you after the fact on this path.
Legacy plans overflow differently. Once the weekly grant is exhausted, you can continue on demand, and Cursor bills that usage directly. The catch is that on-demand has to be switched on in your billing settings beforehand.
So "what happens when the allowance runs out" has two different answers. The one that applies to you depends on a plan choice you may have made years ago. Check which family you are in before planning around either behaviour.
Both allowances reset weekly rather than daily. Monitoring consumption partway through the week is the only way to avoid an unplanned stop, because neither model warns you in advance.
Can you link an account for a bigger allowance?
Yes, but only on legacy Cursor plans. Linking grants additional Grok Bot usage while leaving your existing Cursor plan exactly as it is.
Four individual subscriptions qualify: SuperGrok, SuperGrok Plus, SuperGrok Heavy and X Premium+. You can also sign in using a Grok account that holds an assigned seat on a self-serve Grok Business plan.
Here is where teams waste money. The allowances do not add together. Grok Bot uses whichever source grants more weekly usage. Paying for a high Cursor tier and a high linked subscription gains nothing beyond the larger of the two.
AiBuildrs regularly finds teams paying twice for one allowance. SuperGrok Lite is a separate case, because it does not include Grok Bot at all, so linking it achieves nothing whatever.
The linking route is also exclusive to legacy accounts. The X Subscription handles entitlements through its shared pool and does not support this mechanism. Metered activity still reports against the single Cursor account in every case.
What do you lose by switching to The X Subscription?
Switching is optional for existing legacy customers, so nobody is forcing the move. If you do switch, the documentation is blunt. A completed unification is permanent, and support cannot undo it.
Three things change at once. Your usage moves to the shared weekly pool. Your overflow moves from on-demand billing to prepaid credit. Your linking route disappears, because a SuperGrok link is no longer part of the arrangement.
That third change is the one that catches people out. If your current allowance is effectively set by a linked subscription rather than by your Cursor plan, switching removes the very thing providing your headroom.
Work out which source currently sets your allowance before deciding. AiBuildrs runs that check before a client commits to either plan family, because the answer often reverses the obvious choice.
There is no route back afterwards. Support cannot restore legacy terms. This is a decision to make once, deliberately, with your actual usage pattern in front of you.
Frequently Asked Questions
Is there a Grok Bot limit for free users?
There is no limit for free users, because there is no access at all. Grok Bot is not included on the Free or Plus tiers of The X Subscription. There is no free legacy Cursor route to it either, so both plan families treat the agent as a paid entitlement. A free account therefore has no quota to spend rather than a small one to manage carefully.
How many Grok Bots can you have?
The product does not work in terms of multiple bots. Grok Bot is a single agent tied to your account, and your allowance governs how much you use it rather than how many instances run. Signing in with the same account across devices draws on that one allowance. That is why macOS and iOS share a single usage bucket between them rather than holding separate ones.
Do you need a subscription for Grok Bot?
Yes. You need either The X Subscription at Premium, Super or Ultra, or a paid legacy Cursor plan. There is no standalone subscription for the agent by itself, so the allowance always arrives bundled into a wider plan. Cursor Teams includes it too, which covers team seats on the legacy side. Larger organisations arrange access through an account executive or an account manager instead of self-serve signup.
How do you get more Grok Bot usage?
It depends on your plan family. On The X Subscription you add prepaid credit, which covers usage once the shared weekly pool is empty. On a legacy Cursor plan you enable on-demand billing instead, and Cursor charges that usage directly to you. Legacy accounts can also link a qualifying subscription, though that raises the allowance rather than adding to it. Waiting for the weekly reset is the other option.
Does usage reset daily or weekly?
Weekly, on both plan families. The shared pool on The X Subscription refreshes weekly rather than daily. So does the separate grant on legacy Cursor plans. A heavy day early in the week therefore reduces what is available for the rest of it. Neither model warns you as you approach the limit, so check your figure partway through the week.
Can you combine a Cursor plan and a linked account?
No. The two allowances never stack or combine into a larger total. Grok Bot evaluates your legacy Cursor plan and your linked subscription, then uses whichever grants more weekly usage. Linking acts as an entitlement trigger rather than as a way to increase capacity. Paying for both therefore only buys you the larger of the two figures, which is a common and avoidable waste.
Where do you check remaining usage?
In your Cursor account, because that is where Grok Bot usage is metered regardless of plan family. Your Grok account and your X account will not display the figure, which is a common source of confusion. The same account also holds your prepaid credit balance or your on-demand billing setting, depending on which plan family applies to you. Check it before a heavy week rather than during one.
Can you switch back to a legacy plan afterwards?
No. The documentation states that moving to The X Subscription is permanent and that support cannot reverse it. Your legacy weekly grant, your on-demand billing route and your ability to link an outside subscription all stop applying once the move completes. Decide before switching, because there is no path back to the previous arrangement at all. Check which source sets your allowance today before you commit.
How big is the weekly pool?
Neither xAI nor Cursor publishes the size of any pool or grant. The documentation describes the relative ordering only. Super and Ultra carry larger pools than Premium, and Ultra holds the highest legacy grant. It attaches no numbers to any of them. Any article quoting a specific figure is not sourcing it from the official pages, so treat those claims as unverified.
Executive Summary
Grok Bot usage is metered on your Cursor account. That holds whichever plan family you are on. It is not metered on your X or Grok account.
On The X Subscription, Grok Bot shares one weekly pool with Cursor and the Grok apps. When the pool empties, further usage comes from prepaid credit that you top up.
On a legacy Cursor plan, you get a separate weekly grant. When that runs out, you can keep going on demand if the setting is enabled. Cursor bills it directly.
Linking a qualifying outside subscription raises a legacy allowance. The two never add together. Switching to The X Subscription is permanent, and it removes the linking route.
What Should You Do Next?
Open your Cursor account and find which plan family you are actually on. Most confusion about limits comes from reasoning about the wrong meter.
If usage limits are shaping how your team works rather than the other way round, the constraint may be the plan architecture. Talk to AiBuildrs about what the work actually needs.
People Also Read
- When Should You Build Custom AI Solutions vs Buy?
- What Are the Best AI Consulting Services for Mid-Market Businesses?
About the Author
Jerry Jariwalla is the founder of AiBuildrs and creator of the Growth Signal Intelligence framework. With over 22 years in digital marketing and multiple successful business exits, Jerry has spent the past decade leading AI implementation programs for mid-market businesses across professional services, recruitment, membership organizations, and traditional industries. AiBuildrs has completed over 200 successful AI implementations using a workflow-first methodology and is trusted by leaders at YPO, Vistage, Tiger 21, and C12 executive peer organizations.
Expertise: AI Strategy, AI Implementation, Workflow Automation, Custom AI Development, Voice AI, Offshore Engineering, B2B Sales Intelligence, Mid-Market AI Adoption
Connect: LinkedIn
Disclaimer: This content is for informational purposes only and does not constitute professional business or technology advice. ROI outcomes vary based on industry, existing systems, and implementation commitment. Contact AiBuildrs for a consultation regarding your specific situation.
Jerry Jariwalla
Jerry Jariwalla, Founder & CEO of AiBuildrs, builds custom AI infrastructure, voice AI, automation systems, and The AEO Engine. View Jerry Jariwalla's Full Profile →