Grok chat, Build, Imagine, and the API: pick a surface

You open Slack at 4:40 p.m. on Friday and count three receipts in one thread: SuperGrok on the phone, a $25 API top-up the intern bought at lunch, and Imagine still flashing try again later after 11 poster variants. The Tuesday meetup flyer still reads Analtyics in 72-point type. Finance will ask which of those three purchases was the real one, and nobody on the thread can answer without opening four different sites.

This is Part 8 of the Grok series, and the start of the product map. Part 1 named the company and the product. Part 2 walked the chat apps. Part 7 drew the line where Grok should not be the tool. Here the job is narrower: stop paying the wrong bill and opening the wrong app. xAI (some public pages currently say SpaceXAI; branding names move) ships one model family through four surfaces. They do not share a wallet, a quota, or a “done” definition.

What you’ll learn

• The four Grok doors in plain English: chat apps, Grok Build, Imagine, and the Console / API
• What each one is for, who should open it, and which bill it hits as of writing
• Why a SuperGrok (or X paid) chat plan does not refill API credits or Imagine studio capacity
• A Friday chooser you can run in one breath before you install anything else
• Mix-ups that burn money, leak keys, or send a folder agent into a job that only needed a paragraph

Plan names, quotas, and button labels move. Treat this as a dated map. Re-check grok.com, x.ai/build, grok.com/imagine, and the Grok FAQ the week you roll this out for a team.

Four doors, four jobs

People say “I used Grok” the way they used to say “I used Excel.” That sentence hides the object. Did they type in a chat box? Did an agent open a repo? Did a studio render a still? Did a script call an HTTP endpoint? Those are four jobs. Mixing them is how you get Priya’s Friday: three receipts, one misspelled flyer, and a standup that starts with “which Grok?”

Hold the split in your head before you touch settings.

If you remember one row, remember the last column. The surface follows the job. The brand name on the icon does not.

Rule of thumb: Chat money and API credits are separate systems. Do not promise they share a wallet. Confirm in the Console and in your chat plan page before you tell finance “we already pay for Grok.”

Chat apps (grok.com, mobile, X)

Chat is the default door, and it is the right door for a huge share of real work. You type, you attach a file you are allowed to share, you read the reply, you push back, you copy something into an email. The unit of work is a conversation. That sounds small. It covers status notes, metric definitions, “explain this error like I am the analyst who has to present it,” and the first pass on a messy brief.

As of writing, that conversation lives in three places that feel similar and are not identical: grok.com in a browser, the Grok iOS and Android apps, and Grok inside X. Part 2 of this series is the map of those apps. The product-map point is the job, not the icon. If the artifact is language or judgment inside a thread, stay in chat. Do not graduate to a terminal agent because a blog post made folder access sound more serious.

What chat is good at

Use chat when you still own the paste. Draft the meetup blurb from five ugly bullets. Turn a 12-line Slack dump into three options with risks. Ask what “active store” should mean before anyone builds a chart. Critique a slide outline. Translate a SQL error into a sentence a product manager can use. Capture a voice note on the train and clean it up at a desk. None of that needs a repo, a render queue, or a key that starts with xai-.

What chat is awkward for

Chat is awkward when the unit of work is a tree of files that must stay consistent. You can paste a function. You are still the glue: copy, apply, re-paste the traceback, hope you did not miss the helper two folders down. Chat is also a weak place to pretend you “made the poster.” A long description of a flyer is not a flyer. And chat is a terrible place to stash an API key “so the intern can try the docs.” That is a Console job with a secret manager, not a thread.

Work caution still applies. Part 6 is the privacy pass. A personal grok.com login on cafe Wi-Fi is not your company’s mail system. If the thread has a vendor redline in it, you are in the wrong door. That story is the next map part. For this part, the tell is simpler: if a human is talking to Grok, you are in chat. If software is talking to Grok, you are not.

Grok Build is a folder agent

Grok Build is the terminal coding agent. You install a grok CLI, you cd into a project, you let the agent read the tree, and you review diffs before anything lands. That is a different object than a chat bubble. The model family can be the same. The blast radius is not.

Vendor pages as of writing put Build at x.ai/build, with an overview in the Build docs. Launch eligibility has been described as SuperGrok and X Premium Plus. Re-verify before you tell a team they “already have it.” Headless runs, plan mode, AGENTS.md, skills, and MCP belong in the Build tutorial later in this series. The map point is shorter: open Build only when a real project folder is the work.

Open Build when the folder is the point

Good first jobs: “Where is ship_date parsed in this repo?” “Propose a one-function fix for the CSV export, then stop.” “List the tests that touch billing.” Bad first jobs: rewrite the meetup blurb, generate the flyer, or “clean unused files” on a laptop that still has yesterday’s production clone on the desktop. An agent that can edit a tree will edit a tree. Chat will ramble. Build will touch disk.

If you do not have a sandbox repo, you do not have a Build task yet. Clone a toy. Commit first. Then talk to the agent. That ritual is the whole safety story in one paragraph, and it is why Build is a door, not a skin on grok.com.

Imagine is a studio

Imagine is where images and short video come from. The consumer studio lives at grok.com/imagine and in the apps. Quality Mode, as of writing, is Imagine Image 2.0 (vendor GA note: August 7, 2026). There is also an Imagine family on the API, with ids such as grok-imagine-image-2.0. Those ids are not a chat model with extra adjectives. They are a different product with different meters.

Priya’s 11 poster variants were an Imagine job. The misspelled Analtyics is the usual studio fail: on-image text is the hard part, and a chat model will happily describe a perfect poster while the pixels say something else. You inspect the still. You do not paste the description into Slack and call it shipped. The Imagine tutorial later in the series starts from a brief that names subject, setting, style, and any words that must appear. This map only needs the door: if the output is a picture or a clip measured in seconds, open the studio. If the output is a paragraph, stay in chat.

Throttles are local to the control you are in. A chat plan, a mobile quota, and an API image call can each say no for a different reason. Buying Console credits because the phone studio stalled is how you get receipt number two and still no flyer. Check which surface returned the error before you open a second wallet.

Console is for apps

The xAI Console at console.x.ai is the builder control room: API keys, usage, credits. The HTTP base URL as of writing is https://api.x.ai/v1. Docs live under x.ai/api. The Console is for software that calls Grok on a schedule, in an IDE plugin, or behind your own UI. It is not a second chat box with a sterner login.

You do not need a key to finish the rest of this map, or to write, or to try Imagine in the consumer studio, or to run Grok Build under a chat plan that includes it. Opening the Console “because serious teams have keys” is how keys land in screenshots. Opening the Console because you are shipping a small internal bot that posts a daily count is a real reason. Part 11 of this series is the light first request. Today, the only rule is: no app, no key.

Billing is the surprise that keeps showing up in finance Slack. Chat subscriptions (SuperGrok, paid X, whatever the live SKU is called this month) pay for a human talking to Grok. API credits pay for tokens your code spends. They do not refill each other. The intern’s $25 top-up did not unstick Imagine on Priya’s phone. It also did not add Build minutes. It bought token headroom for a script that did not exist yet.

Worked chooser (Priya’s Friday)

Walk Priya’s afternoon as four tickets, not one panic. The meetup is Tuesday at 6:30 p.m. in the 14th-floor training room. Ops wants a blurb, a door flyer, a tiny RSVP script in the events repo, and (someone said this in passing) a Slack bot that posts signups at 9:00 a.m. That last one is how wallets multiply.

Ticket 1 is the blurb. Five bullets in Slack, one of them still says “Tuesay.” Open grok.com on the work account. Paste the bullets. Ask for a 90-word blurb with the room number and the 6:30 p.m. start, and tell it not to invent a speaker. You edit two sentences so it sounds like Ops. Time: 8 minutes. Surface: chat. Bill: the chat plan you already had.

Ticket 2 is the flyer. Subject: Tuesday analytics meetup. Setting: cream paper on a cork board, not a cinematic city. Style: print, high contrast, words must be spelled. Open Imagine. Generate. Read every letter on the still. The 11th variant is where Priya should have stopped and fixed the brief (name the words, ban script-style lettering) instead of buying API credits. Surface: Imagine. Bill: whatever Imagine quota that phone login has. If it throttles, you wait or you switch accounts on the same studio. You do not open console.x.ai to unstick a JPEG.

Ticket 3 is the RSVP script. There is a folder, events-rsvp/, with one Python file and a broken date parse on meetup_on. That is Grok Build. Clone a copy. Commit. Ask a read-only question first: where is the date parsed. Then one tiny change. Review the diff. Surface: Build. Bill: the chat-plan eligibility for Build, not the $25 API top-up, unless you have chosen to run Build against an API key on purpose.

Ticket 4 is the Slack bot. That is software. It needs a key, a place to store the key that is not Slack, a spend cap, and someone who will own retries. That is the Console, and it is not a Friday-at-4:40 job. Park it. If you do it later, Part 11 is the first request. If you skip the parking step, you get the intern’s top-up and a gist waiting to happen.

Chooser in one breath, the one you can say before standup:

1. Is the output words a person will edit? Chat.
2. Is the output pixels? Imagine.
3. Must a project folder change under review? Grok Build.
4. Is the caller a program that will run without you? Console / API.

If two answers are yes, split the work. The blurb and the flyer are two tickets. Do not make Build “also write the poster.” Do not make chat “also push to main.”

Common mistakes

How to practice / next step

Pick one real task from your week. Write one sentence: “The output is ___.” Then open only that door. If you cannot finish the sentence, you do not have a Grok task yet. You have a pile.

If your sentence is “a reply,” stay in chat and reuse the habits from the first 30 minutes. If it is “a still,” bookmark Imagine and wait for that tutorial. If it is “a diff,” wait for Grok Build. If it is “a bot,” wait for the Console part.

Next in this series, still on the product map: Grok models chooser: 4.5, 4.6, and when to switch. Version numbers are not a fourth door. They sit inside the door you already picked. Start from the Grok series hub when that part is up. For a wider set of paths, Learn lists the other tool families on this site, including ChatGPT, Claude, and Gemini. Same idea there: name the surface before you name the model.

Quick recap

• Say the job before you say Grok: words, pixels, a folder, or an app
• Chat apps (grok.com, mobile, X) are for a human in a thread
• Grok Build is a terminal agent in a project folder you review
• Imagine is a studio. A description of a poster is not a poster
• The Console is for keys and token bills. Skip it until you ship software
• Chat plans and API credits do not share a wallet as of writing. Re-check before you buy a second time
• Split mixed Friday piles into tickets. One door per ticket

Sources

Research and further reading used for this article:

• grok.com (consumer chat surface)
• Grok Imagine (consumer studio for images and short video)
• xAI: Grok Build (terminal coding agent product page)
• xAI docs: Grok Build overview (what the CLI is for)
• xAI API (builder entry and current model list to re-check)
• xAI Console (keys and API credits, separate from chat plans)
• Grok FAQ (plan and product questions that move; read the week you buy)
• Analytics Made Simple: Learn (related paths on this site)

Merch on Etsy

Open store →

Naive Bayes Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Bayesian Mouse Pad View on Etsy → Mute Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, You're On Mute View on Etsy → You're On Mute White Ceramic Coffee Mug, Data Science Mug, Data Mug, Analytics Mug, Statistics Mug, Programming Mug, Gift Mug, Coffee Mug View on Etsy → Boxplot Mouse Pad, Data Science Mouse Pad, Analytics Mouse Pad, Box Plot, Whisker Plot View on Etsy →