TraceCheck.dev

xAI · Product identity and entitlement

Grok Bot vs Grok Build: Access, Usage Pools, and Limits

This page covers product identity, entitlement, and pool separation. Grok Build’s shared weekly SuperGrok pool, reset, Extra Usage Credits, and API RPS/TPM stay on the Grok Build usage-limits guide.

Last verified · Grok Build

Usage evidence reviewed . Other product facts retain their earlier verification date.

Direct answer

Is Grok Bot the same allowance as Grok Build?

Not the same product
Fact Grok Build is a grok.com / Grok-apps coding product on the shared SuperGrok weekly pool. Grok Bot is a separate durable-bot product with its own weekly usage.
Cursor Bot is not SuperGrok Build
Fact Cursor-included Grok Bot does not imply a SuperGrok Build weekly-pool entitlement. Cursor says linking SuperGrok is a Bot usage grant on the Cursor account and does not change the Cursor plan.
API is a third system
Fact xAI API grok-build-0.1 uses RPS/TPM, not the SuperGrok weekly pool and not Bot weekly usage.
Which plans include Bot
Unknown — conflicting xAI Bot FAQ, Cursor help, and the August 26 xAI news post currently list different eligible plans. TraceCheck does not pick a winner.
Last verified
Sep 8, 2026, 8:00 PM UTC

Build, Bot, and API compared

Official relationships only. Shared branding is not treated as a shared quota.
SurfaceProvider / access pathEntitlement sourceConsuming poolResetExhaustionUnknowns
Grok BuildxAI. Grok website and apps; listed in Settings → Usage alongside Chat, Imagine, and VoicePaid Grok / SuperGrok subscriptionOne shared weekly SuperGrok usage pool across Grok products, including BuildWeekly, on the account schedule shown in Settings → Usage. TraceCheck does not invent one UTC reset.Paid features pause until reset. Extra Usage Credits, a plan upgrade, or Auto Top Up can continue paid use. Free-tier Chat and Voice remain on their own schedule.Fixed numeric Grok Build, SuperGrok, and free-plan subscription quotas; One universal reset day or hour for every subscriber
Grok BotxAI, signed in through a Cursor account. Grok Bot desktop and companion apps. Official Bot FAQ does not describe Bot as grok.com Grok Chat.Official sources currently disagree on which SuperGrok and Cursor plans include Bot. Cursor help says every paid individual Cursor plan and Cursor Teams include it, and that linking SuperGrok or X Premium+ is a usage grant, not a Cursor plan change. xAI Bot FAQ lists SuperGrok Plus/Heavy, Cursor Pro+/Ultra, and Cursor Teams. An August 26 xAI news post lists SuperGrok, Cursor Pro, and Cursor Teams.Own weekly Bot usage. Cursor says Bot usage is metered on the Cursor account, not on Grok or X. xAI news says Bot usage is separate from existing Grok and Cursor plan usage.Weekly included usage. Numeric Bot allowance is not published.Cursor says extra Bot usage can continue on shared on-demand spend if on-demand is enabled. xAI FAQ says eligible accounts can add on-demand usage billed from model and token cost.Numeric weekly Bot allowance by plan; Which current plan list is authoritative while official sources conflict; Whether Bot usage appears in grok.com Settings → Usage
xAI APIxAI. Developer API account; grok-build-0.1 and aliasesSeparate API account, not a SuperGrok or Cursor Bot grantPer-model RPS and TPM. Tier 0 for grok-build-0.1 is 37 RPS and 10,000,000 TPM.Continuous API rate limits, not a weekly SuperGrok resetHTTP 429 when RPS or TPM is exceeded. This does not consume or reset the SuperGrok weekly pool.How the Settings → Usage API product line relates to developer API RPS/TPM

Do these share usage?

There is no universal Grok quota.
PairShare a pool?Basis
Grok Build and Grok BotFact NoOfficial Bot docs and Cursor help describe Bot as its own weekly usage, separate from Grok plan usage and metered on the Cursor account.
Grok Build and xAI APIFact NoAPI RPS/TPM is a third system. HTTP 429 on the API is not SuperGrok weekly exhaustion.
Grok Bot and xAI APIFact NoNo official source treats Bot weekly usage as API RPS/TPM.

Common confusion

Unknown — undisclosed Numeric weekly Bot capacity by plan is not published. User-reported Bot dollar bars are demand evidence, not Fact.

Official source conflict

Official sources disagree

Unknown — conflicting Which SuperGrok and Cursor plans currently include Grok Bot

  • Source A: Grok Bot FAQ — The Grok Bot FAQ lists eligible plans as SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, and Cursor Teams Standard and Premium. If both Cursor and SuperGrok subscriptions exist, Grok Bot uses whichever has more usage.
  • Source B: Cursor Grok Bot plans and billing — Cursor help says Grok Bot is included on every paid individual Cursor plan and Cursor Teams, and that linking individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ is a usage grant on the Cursor account. SuperGrok Lite, SuperGrok Team, and SuperGrok Enterprise are not included.
  • Applies to: Users deciding whether a current SuperGrok or Cursor plan includes Grok Bot
  • Decision impact: Do not treat one eligible-plan list as settled Fact. Build vs Bot pool separation does not depend on resolving this list. Cursor-included Bot still does not imply SuperGrok Build weekly-pool entitlement.
  • TraceCheck status: Unresolved — Derived outputs must not treat one side as settled Fact.
  • Current interpretation: TraceCheck records that official Bot plan lists currently disagree. The August 26 xAI news post lists SuperGrok, Cursor Pro, and Cursor Teams, which matches Cursor help more closely than the Bot FAQ list and remains a third official description.
  • Last checked Sep 8, 2026, 8:00 PM UTC

Freshness

Named sources: xAI Grok usage FAQ, Grok Bot FAQ, August 26 Grok Bot plan expansion, Cursor Grok Bot plans and billing, xAI API rate limits, and Grok Build 0.1 docs. Review trigger: a change to Bot eligible-plan lists, Cursor Bot metering, or the SuperGrok weekly-pool FAQ.

Last verified Sep 8, 2026, 8:00 PM UTC

Related plans, limits and decisions

Grok Build