Grok Subscription vs xAI API Pricing: Which Route Pays for What?

Short answer: choose a Grok product route when a person is working through an account-authenticated Grok surface. Choose the xAI API when software sends requests with an API key. The same organization may use both, but a subscription allowance, Extra Usage Credits, workspace licenses, and an API team's metered bill are different ledgers.

The public consumer price anchors are Free at $0 per month, SuperGrok at $30 per month, and SuperGrok Plus at $100 per month. SuperGrok Lite and SuperGrok Heavy remain named routes in the official comparison table, but their live checkout terms should be checked rather than guessed. This page explains which route pays; use Grok pricing for the maintained purchase matrix.

Choose the ledger before the plan

Actor, credential, and billing owner are more reliable than a shared product name. An account session or supported organization login points toward a Grok product allowance. A direct API key points toward the API team's ledger. Grok Build can sit on either side, so its resolved authentication method matters more than the word Build.

Consumer plans, X access, and Extra Usage Credits

Free is the no-cost starting route. SuperGrok is the main $30 monthly individual upgrade, and SuperGrok Plus is the $100 monthly route for substantially higher product usage, 1080p video creation, priority access, and early features. The comparison table also retains SuperGrok Lite and SuperGrok Heavy. Because the public page does not present those two with the same simple headline price, treat their checkout terms as live facts rather than filling the gap with an old number.

Paid Grok use draws from a shared weekly allowance across eligible Grok products. The Usage surface shows the reset schedule and a product breakdown. Compute-heavy video or long coding work can drain more of that allowance than a short chat, so there is no honest universal conversion from a monthly fee to a message quota. This guide intentionally does not invent one.

X-linked access is its own entitlement path. Grok can retrieve relevant X subscription benefits only after the correct X account is connected to the xAI account. X remains responsible for its subscription relationship, while Grok web, Apple, and Google purchases follow their own billing owners. Signing in with a different account can make a valid benefit appear missing without turning the purchase into API spend.

Extra Usage Credits are another separate route. They extend eligible paid Grok features after the included weekly allowance runs out, and Grok-side Auto Top Up can replenish that balance within the user's chosen cap. They do not become reusable credits in xAI Console. Conversely, API prepaid credits do not refill the consumer weekly pool.

Use Extra Usage Credits for occasional product overflow. If overflow is routine, compare a higher Grok tier. If the work is initiated by software, uses API keys, or serves customer traffic, stop treating top-ups as a subscription decision and forecast the API workload instead.

What Grok 4.6 API billing funds

The direct API route begins in xAI Console. A developer creates or selects an API team, adds prepaid credit or approved invoiced capacity, creates an API key, and sends requests from software. The team owns the usage record and invoice, so a personal or workspace Grok purchase should not be assigned as the cost owner for a production service.

Grok 4.6 has two published token bands. The long-context threshold is based on prompt length, and once the prompt reaches the threshold the long-context prices apply to all tokens in that request.

A request can create more than one kind of charge. Model input, cached input, reasoning, and output tokens remain billable, while autonomous server-side tool use can add several invocation charges during one user task. Web Search, X Search, and Code Execution therefore belong in the workload estimate even when the base model price looks predictable.

Long context and Priority Processing are separate decisions. Long-context pricing is triggered by prompt length. Priority Processing is requested through the priority service tier and is billed at two times the applicable standard token rates only when the response confirms that tier. Cache discounts are applied before the priority multiplier. Do not merge either condition into the short-context base row.

The Grok 4.6 launch announcement separately says a fast variant is twice the price. The announcement's fast label and the API documentation's Priority Processing label should not be silently treated as interchangeable, and neither should overwrite the standard Grok 4.6 price. Check the selected model, requested service tier, returned service tier, and per-request cost before assigning the premium.

Use Grok 4.5 vs Grok 4.3 for the historical model-selection boundary it documents. Use Grok web search vs X search when the remaining question is which search tool the workload needs. For current API estimates, start with Grok 4.6 and the official pricing page.

xAI exposes per-request cost data, and Usage Explorer can group consumption by key, model, token type, or billing item. Track prompt length, cache hits, output length, retries, reasoning, tool loops, media units, and request volume. Prepaid credit supplies a natural stop when invoiced billing is disabled; approved monthly invoicing and its spending limit are separate team controls.

Grok Build crosses both routes

Grok Build is the clearest example of why the credential decides the bill. On first interactive launch it can open a browser for account authentication. Enterprise deployments can also use device or organization identity. Those routes use the account or workspace relationship and belong on the Grok product side of the decision.

Grok Build can instead resolve an API key, especially for scripts, CI, bots, and other headless automation. That path calls the direct API and should be forecast from the selected model, prompt and output tokens, tool calls, processing tier, and API-team controls. A Business or Enterprise login existing in the same organization does not make API-key requests part of a seat.

Current Grok Build documentation identifies Grok 4.6 as the model that also runs directly through the API. That shared model does not merge the commercial routes. Verify the resolved credential before attributing the cost, and treat short-lived included-usage promotions as route-specific rather than reusable API credit.

Business, Enterprise, and mixed organizations

Business is a managed people-and-workspace route. The official page lists it at $30 per month per user and pairs it with team and seat management, consolidated billing, role controls, domain management, analytics, and Grok Build. It fits organizations that need governed interactive use rather than a collection of personal subscriptions.

Enterprise remains a sales-led route with custom organization, security, identity, support, and deployment terms. Because its public price is not a numeric self-serve rate, budget it as a contract discussion. Do not turn Enterprise into a guessed per-seat number or assume the contract includes a general API allowance unless the order form says so.

An xAI API team is a developer billing and credential boundary. It owns API keys, prepaid balances, invoiced usage, usage exploration, and API invoices. Business and Enterprise may share administrators with an API team, but their workspace licenses and the API team's meter remain separate unless a reviewed contract explicitly changes that boundary.

Many organizations therefore need both: seats for people who research, write, analyze files, create media, or work interactively in Grok Build, plus an API budget for customer features, scheduled jobs, internal automations, CI agents, and services that run without a person initiating each request. Track the two routes as different line items with different owners and stop controls.

Final decision check

Before paying, write down who initiates the work, which credential authenticates it, which account or team owns the charge, which unit drains, and which control stops overspend. If an estimate mixes a weekly percentage with API tokens, treats Extra Usage Credits as API prepaid credit, or assumes a Business seat pays for API keys, the routes are still being conflated.

Start with Free when the job is exploratory personal use. Choose a paid consumer tier when one account needs more Grok product capacity, and compare Lite, SuperGrok, Plus, or Heavy only through the live purchase surface. Use X-linked access only for the benefits attached to the correctly connected X account. Choose Business or Enterprise when people need managed organization access.

Choose the xAI API for software-driven Grok 4.6 workloads, API keys, automation, and per-request cost tracking. Buy both workspace access and API capacity when people need Grok and systems need xAI models. Finish by checking Grok pricing for maintained plan and route facts; the durable rule is that product access and direct API usage have separate billing owners.