Grok Pricing: Free, SuperGrok, Business, and API

Buying path

The safest starting point is the free Grok assistant because it proves whether real-time web and X research, voice, connectors, files, and basic creation belong in the reader’s weekly routine. A paid route is justified only after a repeatable task runs into capacity or requires a feature that the free account does not reliably expose.

The lowest paid tier is a light-use lane, while the standard paid subscription is the more useful benchmark for recurring research, creation, and coding work. Both sit inside the consumer account rather than a developer console. The buyer should judge them by the weekly mix of simple chats and compute-heavy tasks, not by a monthly price alone.

Paid Grok usage is deliberately flexible: eligible activity draws from one weekly pool instead of isolated daily buckets. That helps a user concentrate capacity on the product they need most, but it also means a video, long coding task, or intensive research run can consume a different share than a short conversation.

Upgrade triggers

Upgrade when the weekly allowance repeatedly interrupts approved work, not merely because a higher tier advertises more capability. The practical trigger is lost output: research that cannot finish, creative work that pauses during revision, or coding sessions that cannot reach review and verification before the reset.

Extra Usage Credits suit occasional spikes because they are used after the included weekly pool. They are less attractive as a permanent habit because official guidance says their per-action economics are worse than included subscription usage. If top-ups become routine, compare the next subscription tier against the real monthly workload.

The highest individual tier belongs to sustained, high-compute use and demanding model access. It should not be the default for ordinary chat. A buyer should first measure how much of the weekly pool goes to research, Imagine, Voice, and eligible Build work, then decide whether more included capacity is cheaper than repeated credits.

API and team boundaries

The xAI API is a separate developer budget. Grok and API access can share an account identity, but official documentation gives them distinct billing systems. API calls consume prepaid credits or invoiced usage at model and tool rates; they do not consume the consumer weekly pool, and a Grok subscription does not grant general API credit.

Grok Business is the self-serve team route for licensed workspaces, centralized billing, connectors, and role controls. Enterprise is the sales-led route for stronger identity, retention, audit, encryption, data-plane, and support requirements. Neither route should be selected only to obtain more personal usage without a genuine organization need.

Grok Build can be reached through eligible account subscriptions, while its models can also be called through the separately metered API. X Premium-linked benefits form another consumer route controlled by X. These paths may expose overlapping capabilities, but their billing owner, permissions, and usage meter must remain distinct.

Final pricing check

Before paying, inspect the actual checkout channel. Web, iOS, Android, and X can present different billing owners, taxes, localized prices, and monthly or yearly commitments. Confirm the total charge rather than relying only on a displayed monthly equivalent, especially for a high-capacity yearly purchase.

Then inspect the Usage page. Record the weekly reset, current product breakdown, and Extra Usage Credits balance. Confirm that top-ups are available in the intended channel, understand their expiry, and decide whether automatic top-up limits protect the budget or simply hide a tier mismatch.

Finally, separate permanent access from promotions. Limited-time Grok 4.5 availability, free Grok Build use, partner access, and regional launches are useful trials but not durable plan entitlements. The purchase should still make sense after the promotion ends and without assuming that consumer capacity can pay an API invoice.