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

Short answer: buy a Grok or SuperGrok subscription when a person is working through an account-authenticated Grok surface. Use the xAI API when software makes requests with an API key. The same xAI account can reach both, but xAI says Grok billing and xAI API billing are separate.

This page is the decision guide, not the maintained price matrix. Check Grok pricing for current consumer, Business, and API purchase routes after you know which ledger should pay.

Choose by actor, credential, and ledger

The credential is the safest tie-breaker. An account session or supported OAuth path points toward the Grok product allowance. A direct XAI_API_KEY request points toward the API team's ledger. Product labels can overlap, but the credential and billing owner reveal which budget is actually being used.

What a Grok subscription funds

A paid Grok plan funds higher access for a user across Grok products. That can include interactive chat, real-time web and X search, file work, Imagine, Voice, and eligible Grok Build use. The subscription buys product access and capacity for the account; it is not a portable balance of general developer-console credits.

Account ownership matters. A subscription bought on grok.com is managed through Grok billing, mobile purchases follow the relevant app-store relationship, and X-linked benefits depend on connecting the correct X account. Signing into another account can make a valid entitlement appear missing. Teams should avoid personal-account purchases when the organization needs controlled assignment, offboarding, and shared administration.

Plan names, regional prices, promotions, and feature limits can change independently. Compare them only after choosing the subscription route, then use the canonical pricing page for the live figures instead of treating one headline price as an API cost estimate.

How the weekly pool and Extra Usage Credits work

Paid Grok use draws from a shared weekly allowance across Grok products rather than an independent allowance for every feature. The Usage view shows the reset schedule and a product breakdown. Compute-heavy video or long coding work can consume more of the pool than a simple chat, so message counts are not a reliable universal unit.

The consumer Usage view may show a product label called API alongside Build, Chat, Imagine, and Voice. Do not interpret that label as a general xAI Console credit balance. Account-authenticated integrations can sit inside the Grok product route, while direct API-key requests still use separate API billing. The distinction is credential and ledger, not whether a screen happens to use the word API.

Extra Usage Credits extend eligible paid Grok features after the included weekly allowance is exhausted. They are purchased and tracked on the Grok side, and consumer Auto Top Up can add them subject to a chosen monthly cap. They do not become general API credits. Conversely, buying API prepaid credits or accruing API invoice spend does not replenish or consume the consumer weekly pool.

Use Extra Usage Credits for occasional overflow. If overflow is routine, compare a higher Grok tier. If the work is generated by software, stop treating top-ups as a subscription decision and estimate the API workload instead.

What xAI API billing funds

The API route starts in xAI Console. A developer creates or selects an API team, adds billing capacity, creates an API key, and sends requests from software. xAI tracks API usage, billing, and invoices at the team level, so a personal Grok subscription should not be used as the cost owner for a production service.

Text and code models are generally metered by input, cached input, reasoning where applicable, and output tokens. Media and voice surfaces can use different units. Server-side tools add another layer: web search, X search, code execution, attachment search, and collections search can be billed by invocation or by the additional tokens they process. An agent may call a search tool several times during one request, so one user action is not necessarily one billable tool call.

Use Grok 4.5 vs Grok 4.3 when model choice is the remaining question. Use Grok web search vs X search when search-tool behavior and invocation cost are the real budget driver. Keep maintained dollar rates on the pricing page rather than copying them into this guide.

xAI exposes per-request cost data that includes model tokens and server-side tool invocations, and Usage Explorer can group API consumption by key or model. That makes API cost measurable at the workload level. Track long prompts, cached context, output length, retries, tool loops, media units, and request volume instead of dividing a subscription fee by an assumed message count.

API spend controls also belong to the API team. Prepaid credits provide a natural stop when no invoiced capacity is enabled. Auto top-up can reduce interruptions, while an approved invoiced spending limit can cap postpaid usage. That limit does not stop prepaid credits from being consumed first. Rate limits and per-key throughput controls reduce traffic risk, but they are not substitutes for a dollar budget.

Grok Build sits on both sides

Grok Build is the clearest case where product name alone cannot identify the bill. An interactive launch can open browser authentication and use an account session. In that route, Build is part of the Grok product experience and can draw from the applicable account or workspace allowance.

Grok Build can also run with XAI_API_KEY, including headless scripts, CI, bots, and other automated environments. That is the direct API-key path. The request goes to the API service and should be forecast from the selected model, tokens, tool use, and API-team controls.

The same model family may appear in the interactive product and on the API. That does not merge the commercial routes. Decide whether the job is human-steered product use or repeatable software execution, then verify which credential the client resolved before attributing cost.

Treat free access announcements and promotional model usage as route-specific and temporary. A promotion for Grok Build or a particular integration is not proof that the account received reusable API credits, and it should not become the production budget assumption.

Business access and when to buy both

Grok Business is a managed people-and-workspace purchase. It adds organization-oriented access such as licenses, team and seat management, consolidated billing, role controls, domain management, analytics, and business data handling. It is the right route when employees need governed Grok access or account-authenticated Grok Build.

An xAI API team is a developer billing and credential boundary. It owns API keys, API usage, prepaid balances, invoiced usage, and API invoices. A Business workspace and an API team may share an organization or administrators, but one does not automatically fund the other.

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

For a pilot, assign each workload before purchasing:

• Put named users and interactive sessions in the subscription or Business lane.
• Put keys, services, scripts, background agents, and customer traffic in the API lane.
• Put Grok Build in the lane selected by its resolved login method.
• Review both ledgers when the same team uses both routes.

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 any answer mixes a weekly percentage with API tokens or treats Extra Usage Credits as API prepaid credits, the routes are still being conflated.

Choose a Grok or SuperGrok route for account-authenticated product use. Choose Business when that use needs managed seats and organization controls. Choose the xAI API for software-driven workloads, API keys, automation, and per-request cost tracking. Buy both when people need Grok and systems need xAI models.

Finish by checking Grok pricing for maintained figures, entitlement names, and current promotions. The durable rule is simpler than the tables: subscription capacity funds eligible Grok product use, while direct API-key usage funds a separate API-team ledger.