The Fast, Real-Time Operator With an Edge
Three things moved between October 2 and October 14, 2026, and none of them waited for you. On October 2 grok-voice-transcribe-1.0 reached end of life, so a pin to it now lands on 2.0. On October 12 xAI rebuilt its pricing page around The X Subscription: Plus $8, Premium $30, Super $100 and Ultra $200 a month, Teams from $30 per user. On October 14 grok-voice-latest moved to Grok Voice 3.0 without any action from you. Grok 4.7 is still the flagship at $2/$6 below 200,000 tokens, and it still can’t use the Batch API. So the risk here isn’t the model. It’s your own notes.
The colleague closest to the live conversation
Some questions change by the hour. That’s Grok’s window. And the edge isn’t the cheeky tone everyone talks about. It’s live X context, frontier reasoning, coding agents and media production sitting in one place.
Direct, fast and current
Grok will take a position. That helps when you’re trying to make sense of a live event. It hurts when the confidence runs ahead of the evidence.
- Real-time social context
- Strong engineering orientation
- Less polished corporate default tone
Live signal and high-velocity execution
Breaking narratives. Market reaction. Technical work, rapid prototyping, coding agents, and image and video experiments in the same window.
- What’s happening now
- What developers are saying now
- What can be built or rendered quickly
Recency or candor changes the answer
Reach for Grok when yesterday’s summary isn’t enough. Or when the social reaction is part of the evidence. Or when a blunt stress test makes the work better.
- Live pulse
- Direct critique
- Fast action through Build or Imagine
Map the three dominant narratives about this announcement on X. Show who is driving each one, what evidence they cite and where the narratives disagree. Don’t decide which is true yet.
Now verify the factual core against the company release, filing and any other primary source. Separate confirmed facts, disputed interpretation and unsupported social claims.
A new flagship at the old price, and a discount you can no longer reach
Grok 4.7 shipped on September 21, 2026 at the same price and the same 500k window as Grok 4.6. The new control is reasoning effort: low, medium, high and xhigh, with high as the default. The new limit is a subtraction: it can’t use the Batch API at all. A faster serving of the same model now has a price, $4 / $1 / $12 below 200,000 tokens, and still no ID. Distribution kept moving too. Four third-party catalogs carried Grok 4.6 by August 26. Two more routes, into Word, Excel and PowerPoint and into Copilot Studio, belong to Microsoft, not to xAI, and the cards below take each one in turn.
grok-4.7: none, so batch pricing never applies to the flagshipgrok-imagine-image-quality, 18 days after October 15, 2026; requests then move to grok-imagine-image-2.0 at low quality, $0.01 per image cheaper at every resolutionGrok 4.7 Flagship · September 21
Out on September 21, 2026, and priced exactly where 4.6 was. $2.00 per 1M input, $0.50 cached input and $6.00 output below 200,000 tokens, with a 500k context window. Cross 200,000 tokens and every token in the request bills at the long-context rate. The real change is a dial. Reasoning effort now takes low, medium, high or xhigh, and it defaults to high, so a request you don’t configure is a request on the expensive setting. The other change is a subtraction: the Batch API doesn’t support this model. xAI’s pages don’t agree on its knowledge cutoff, so name the page whenever you quote one.
- Pin
grok-4.7rather than a moving alias - Reasoning effort: low, medium, high, xhigh. Default is high
- No Batch API support, so batch pricing doesn’t reach the flagship
- Region us-east-1 on its model page; rate limits of 150 requests per second and 50,000,000 tokens per minute are unconfirmed as of October 15, 2026
- Text and image in, 500k context, long-context tier at $4 / $1 / $12
- xAI positions it as “Twice as fast, at half the price of comparable models,” which is a vendor claim
- xAI’s developer guide names Grok Build, Cursor, OpenRouter, Vercel and Cloudflare as places it runs, plus the US regional endpoint
- Model card dated September 21, 2026, revision 2026-09-21
Grok 4.6 Demoted, not retired
Grok 4.6 is no longer the flagship, and nobody has told you what it is instead. The dedicated model page still renders with no deprecation marking and no legacy label. The price table still carries a grok-4.6 row. But x.ai/api has dropped it from the pricing tables and the docs models index no longer describes it at all. No retirement date appears on any xAI page. So don’t read the marketing page as a shutdown notice, and don’t read the surviving row as a commitment. Ask xAI in writing how long that row stays.
- Still priced at $2 / $0.50 / $6 below 200,000 tokens, 500k context
- No retirement date published on any xAI surface
- Dropped from the
x.ai/apipricing tables, though that page’s FAQ still names it, and from the docs models index - Its developer guide URL,
docs.x.ai/developers/grok-4-6, now serves the Grok 4.7 Developer Guide - The US regional endpoint still serves
grok-4.6 - Grok 4.5 is a generation further back, still carries a price-table row, and still has its own model card linked from
x.ai/safety - If a workload depends on 4.6 output behavior, start the 4.7 comparison now rather than on the day the row goes
Four surfaces in twelve days Distribution
Grok 4.6 landed on GitHub Copilot on August 14, 2026. Then Amazon Bedrock on August 19, alongside Grok Build on web and mobile. Then the Gemini Enterprise Agent Platform on August 21 and Microsoft Foundry on August 26. Four third-party catalogs in twelve days, and the wave starts at Copilot, not at Bedrock. Count from Bedrock and you lose a surface and flip the order. Bedrock wasn’t new in August either. xAI published a Grok on Amazon Bedrock listing on June 17, 2026 and Grok on Databricks on June 18. So Databricks is a fifth catalog, it predates the August wave, and only Grok 4.6 on Bedrock was new. Either way the buying question changes. Plenty of organizations can now get Grok through a contract they already signed, without ever signing one with xAI.
- GitHub Copilot August 14, Bedrock August 19, Gemini Enterprise Agent Platform August 21, Microsoft Foundry August 26
- Grok reached Bedrock on June 17, 2026 and Databricks on June 18, 2026
- Copilot access may need enabling in Copilot settings on business and enterprise tenants, as xAI noted at launch
- Check which entity holds the data terms on each platform
Grok in Word, Excel and PowerPoint through the Microsoft Frontier Program September 18 · off by default
This route is Microsoft’s, not xAI’s. Microsoft added SpaceXAI to its subprocessor list on September 10, 2026, and says the models have been available to eligible customers since September 18, 2026. Word, Excel and PowerPoint only. Access sits behind a dedicated admin setting, and Microsoft says the models are currently disabled for all eligible customers until someone switches them on. The exclusion list is longer than people quote. It covers the European Union, the European Free Trade Association and the United Kingdom, plus government clouds (GCC, GCC High and DoD) and sovereign clouds. No end date. And these models sit outside Microsoft’s in-country processing commitments. The upside is the paperwork. Microsoft’s Product Terms and Data Protection Addendum apply, and so does its Customer Copyright Commitment for Grok in Word, Excel and PowerPoint. So the contract question on this route is a Microsoft question. One name trap before you search. The only “Frontier” document on x.ai is the xAI Frontier AI Framework, a safety policy dated June 30, 2026. Different thing, different company.
· Source: Microsoft Learn, “SpaceXAI as a subprocessor in Microsoft Online Services,” checked October 15, 2026. No xAI page mentions this route
- Available to eligible Frontier customers since September 18, 2026, per Microsoft
- Admin path: Copilot, Settings, View all, AI providers operating as Microsoft subprocessors, then SpaceXAI
- That setting is separate from the SpaceXAI entry under AI providers for other large language models
- Excluded: EU, EFTA, UK, GCC, GCC High, DoD and sovereign clouds, with no published end date
- Outside Microsoft’s in-country processing commitments
- Microsoft Product Terms, the Microsoft DPA and the Customer Copyright Commitment apply
- Not the xAI Frontier AI Framework, which is xAI’s own safety policy
- A different mechanism from xAI’s own Office add-ins: see the Workplace Add-Ins section
Grok in Copilot Studio Separate route · US only
Grok is in Copilot Studio, and it got there by a different door. Microsoft announced Grok 4.1 Fast for Copilot Studio on February 19, 2026: preview, US makers only, off by default, under xAI’s own Enterprise terms and DPA. Microsoft says Studio access continues with SpaceXAI as an independent processor, not as a Microsoft subprocessor. That’s the opposite paperwork from the Word route. Now read Microsoft’s warning, because it’s blunt. Its own safety evaluations found Grok 4.1 Fast (Non-Reasoning) less aligned than the other models it tested, with higher risk of harmful content and lower scores on safety and jailbreak benchmarks, and Microsoft doesn’t recommend it for production. xAI switched that model off on its own API on May 15, 2026. Studio’s model list now shows Grok 4.2 as Experimental, in early access environments, United States only.
- Independent-processor route: xAI’s terms, not Microsoft’s
- Microsoft’s safety finding on Grok 4.1 Fast (Non-Reasoning): not recommended for production
- Grok 4.2 listed as Experimental, early access, United States only
- A Studio agent and a Word document reach Grok under different contracts
- Microsoft’s Studio model page is rewritten in place, so confirm directly
Three first-party answers on one cutoff Source conflict
Grok 4.7’s knowledge cutoff depends on which xAI page you happen to open. The model card says a pretraining cutoff of June 2026, plus data generated as late as August 2026 in supplemental training. The dedicated model page says nothing at all. The docs model reference has given May 2026, a figure unconfirmed as of October 15, 2026. A plain date on the page everybody lands on first is the easiest to lift and the easiest to treat as settled. It isn’t settled. Quote a cutoff with the page it came from, and don’t hang a recency assumption on it.
- Docs model reference: May 2026, unconfirmed as of October 15, 2026
- Model card, revision 2026-09-21: pretraining to June 2026, supplemental data to August 2026
- Dedicated 4.7 model page at
docs.x.ai/developers/models/grok-4.7: no cutoff stated - The same three-way split showed up on the previous flagship, so expect it on the next one
- The docs pages are rewritten in place, so confirm directly
A price with no model to call Grok 4.7 Fast · Cursor and Build only
Grok 4.7 Fast now has a price and still has no name you can put in a request. xAI describes it as the same Grok 4.7 model served on faster infrastructure. Below 200,000 tokens it’s $4.00 input, $1.00 cached and $12.00 output. Above that it’s $6.00, $1.50 and $18.00. So it’s twice the standard rate on short requests and one and a half times on long ones. Read “twice the price” as half true. And you can’t buy it on the public API at all. It runs in Cursor and Grok Build, billed through your plan there, and Grok Build’s free tier doesn’t include it. The 4.7 model page lists no fast variant. The Grok 4.6 post announced a fast variant on August 12, 2026 too, and no price or ID for that one appears on the price table. A budget line needs a model ID. This one doesn’t have one.
- $4.00 / $1.00 / $12.00 below 200,000 tokens; $6.00 / $1.50 / $18.00 above
- 2x standard rates on short requests, 1.5x on long-context requests
- Cursor and Grok Build only, billed through the plan; not on the public xAI API
- Not in Grok Build’s free tier
- No model ID on the price table, the developer guide or the 4.7 model page
- Read from docs pages rewritten in place, so confirm directly
The Cursor connection Strategic · same owner
Cursor and xAI are now sister companies, and that changes how you read everything they say about each other. The sequence matters more than any one date. They announced a partnership in April 2026. On July 8, 2026 they shipped together. On August 14, 2026 Cursor said SpaceX had acquired it, finishing the process that started in April. No terms, no valuation. SpaceX had already acquired xAI on February 2, 2026. So the training relationship here is inside one group, not arm’s length. No further terms have been published first-party. The closest thing to a follow-up is a September 22, 2026 xAI post about its own support desk, which mentions a ticket surge after the Cursor merger and nothing else about the deal. Record the rest as not found, not as nothing happened.
- Cursor has been SpaceX-owned since August 14, 2026, with no terms disclosed
- Partnership announced April 2026, joint Grok 4.5 release July 8, acquisition completed August 14
- July 8 wording: xAI said Grok 4.5 “was trained alongside Cursor,” on NVIDIA GB300s, and Cursor said “Today we are releasing Grok 4.5 together with SpaceXAI, our most intelligent model”
- August 14 wording: Cursor posted that it “has officially been acquired by SpaceX,” completing “the acquisition process that started in April, when we announced our partnership with SpaceXAI to accelerate our model training efforts”
- No further first-party detail found, which isn’t the same as none existing
- Since October 12, 2026 The X Subscription sells Grok and Cursor in one plan, and its Enterprise tier runs both from one dashboard and one usage pool
- A buyer evaluating Grok or Cursor should know both products now share an owner, and now share a bill
Grok Bot Eight plans · enterprise controls
Grok Bot looks generally available. xAI has never said it is. It launched August 11, 2026 in early beta for three tiers. By August 26 it covered eight plans. On August 29 it gained an X integration that xAI calls the first version. On September 3 it gained access, network and audit controls so enterprises can govern Bots at scale, and xAI claimed thousands of organizations had adopted it. Then on September 28, forty-eight days after launch, xAI shipped Team Bots and called that public beta in writing. On October 15, 2026, 65 days after launch, no xAI page says Grok Bot has left beta. And one change deserves a procurement owner. xAI’s Bot changelog records on October 11, 2026 that Bots can pay with X Money or Stripe Link. An agent with a payment method is a spending control question, right? Widen your availability claim to the named plans and stop short of calling it GA.
- Eight named plans on August 26, 2026, up from three: SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, and Cursor Teams Standard and Premium
- Since October 12, 2026 The X Subscription bundles Grok Bot with Grok, Cursor and X Premium
- Access, network and audit controls for enterprises since September 3, 2026
- Team Bots, September 28, 2026, described by xAI as available in public beta
- Bot payments through X Money or Stripe Link, and Enterprise Bot computers terminated after 30 days without use: both from a rolling changelog, so confirm directly
- Adoption and isolation statements are vendor claims
- No first-party statement that Grok Bot has left beta: don’t claim GA
Team Bots Public beta · September 28
A Bot the whole team shares, holding one set of context, plugins, credentials and memories. xAI says each person’s conversations with it stay private, and the Bot keeps separate context and memories per user while drawing on skills shared across the team. That is a design claim, not an audit. No Team Bots price is published. xAI says it’s available on Teams and Enterprise plans, and since October 12, 2026 a Teams tier sits on x.ai/pricing at $30 and up per user per month. Here’s the wrinkle a buyer hits in about ten seconds. The page x.ai/grok/business sells a Business tier at $30 per user and lists no Teams tier. The page x.ai/pricing lists Teams and no Business. Same price, two names, two live xAI pages. Ask whether they’re one tier before anyone signs for either.
- Shared context, plugins, credentials and memories across a team
- Per-user privacy and per-user memory are vendor design claims, not tested findings
- No published Team Bots price
- Teams on
x.ai/pricing, Business onx.ai/grok/business: get the tier named in the order form - Still beta, so don’t write it into a dependency
Grok Build Coding agent
A terminal CLI agent, and on web and mobile since August 19, 2026. Plan mode lets you approve, annotate or rewrite the plan before anything runs. Bigger tasks get handed to parallel subagents in their own worktrees. And since September 16, 2026 it keeps memory between sessions as markdown files on disk. The open question is who is entitled to it, and since October 12, 2026 the plan pages say more. The X Subscription lists Build in the Plus tier at $8, beside Grok Chat, Voice and Imagine, and that tier also carries the X checkmark. Premium at $30 carries what xAI calls the benefits of SuperGrok, Cursor Pro and X Premium+. But neither the article nor the pricing page says a standalone X Premium+ subscription includes Grok Build. So that widely repeated claim still has no first-party support. Confirm the plan before you promise it to anyone.
- Approve the plan before it runs
- Parallel subagents and worktree integration
- Persistent memory across sessions since September 16, 2026
- Build listed in The X Subscription from Plus up; standalone X Premium+ entitlement unconfirmed
EU availability isn’t one answer Per surface
One date settled one surface, and people keep quoting it for all of them. Grok 4.5 wasn’t available in EU products or the API console at launch. That gap closed on July 17, 2026, when the developer release notes recorded Grok 4.5 as available to EU users in the API console. Read it for exactly what it covers. One model. xAI’s own API console. July. It isn’t the EU position everywhere, and at least two surfaces are shut as of October 15, 2026. Microsoft says Grok has been available in Word, Excel and PowerPoint to eligible Frontier Program customers since September 18, 2026, and it excludes the EU, EFTA and the UK, along with government and sovereign clouds, with no end date. And Microsoft lists Grok in Copilot Studio for the United States only. Anyone who treats July 17 as settled and then switches Grok on in Word will be wrong about the region they’re standing in.
- July 17, 2026 covers Grok 4.5 on xAI’s API console, not every surface
- The Microsoft Frontier Program route excludes the EU, EFTA, the UK, government clouds and sovereign clouds, with no end date
- Copilot Studio lists Grok for the United States only
- Each third-party catalog carries its own regions and terms
- Establish EU access per surface and per model before promising it
- Source for the Frontier exclusion: Microsoft Learn’s SpaceXAI subprocessor page, not any xAI page
Skills and connectors May 18
Skills reached web, iOS and Android on May 18, 2026. Grok can build documents, decks and spreadsheets, and reach external systems through reusable skills and integrations.
- Persistent expertise
- Business workflow automation
- Permission-aware enterprise use
Office and Workspace add-ins
xAI ships its own free add-ins, and they put Grok inside PowerPoint, Word, Excel, Outlook, Sheets, Slides and Docs. That takes the work story well past X and grok.com. The program started in June 2026. Keep this route apart from the Microsoft Frontier Program route, which Microsoft dates to September 18, 2026. They reach three of the same Office apps by different mechanisms, with different gates and different regional terms.
- Draft and revise documents
- Turn outlines into slides
- Not the same thing as Grok in Copilot through the Frontier Program
- Keep tone and source review explicit
- See the Workplace Add-Ins section for the dated releases and the comparison
A coding agent designed for speed and sustained work
Grok Build moves the product from advice into doing. The /goal command, the session dashboard and the plugin system make the unit of work an outcome, not a run of terminal prompts. Two dates change what a security review looks like. Since July 15, 2026 the agent itself is open source, so a reviewer can read it instead of trusting a description. And since September 16, 2026 it writes memory to disk between sessions, so that review has more ground to cover.
Open source July 15
xAI open-sourced Grok Build: the agent loop, the developer tools, the terminal interface and the skills, plugins, hooks, MCP and subagent systems. That changes what a security review can see. One catch. The announcement page doesn’t state a license, so check the terms in the repository before you build on it.
- Enables local-first use with your own inference
- Read the agent loop instead of trusting a description
- License not stated on the announcement, so verify it
- Repository: github.com/xai-org/grok-build
Web and mobile August 19
Grok Build reached web and mobile on August 19, 2026, the same day Grok 4.6 reached Amazon Bedrock. A coding agent that’s no longer terminal-only is a governance change, not just a convenience, right? The group who can start a long-running agent just got a lot bigger than the group with a configured CLI.
- Not terminal-only any more
- Decide who may launch agents from a phone
- Keep repository permissions as the real control
/goal Long running
A command for handing over a sustained outcome instead of driving every agent turn by hand. This is the CLI’s long-running execution mode, and it isn’t the same thing as consumer Automations.
- Good for bounded projects
- Requires completion criteria
- Use stop conditions
Agent dashboard
Run many coding sessions, watch progress, answer questions and send out more work.
- Parallel engineering
- Central supervision
- Avoid duplicate changes
Plugin marketplace
Extend Grok Build with packaged tools and workflows inside the coding environment.
- Review plugin trust
- Pin required versions
- Keep permissions narrow
Composer 2.5
A specialized coding model you can pick inside Grok Build for fast software tasks.
- Use the model menu
- Benchmark on your repository
- Don’t assume the flagship is always the best route
External coding integrations
Grok subscriptions or models can work through environments such as Warp, Kilo Code and OpenCode.
- Know which tool owns execution
- Check data terms
- Keep configuration documented
Memory September 16
Grok Build now writes notes to disk and keeps them. xAI describes them as conventions, decisions and project facts, stored as markdown, scoped per project workspace and globally. The /memory command opens a read-only browser of the files, and /dream sorts notes into topic files. xAI says it deliberately leaves out task state, temporary conclusions and secrets. Take that as design intent, not as something you’ve tested. Memory applies to new sessions, so run /new or start a fresh grok to pick it up.
- Per-project and global scope, stored as markdown on disk
- Read the stored files with
/memorybefore trusting what the agent remembers - A new artifact that follows a repository around, and a new thing to review when someone leaves
- Applies to new sessions only
Build Mode July 28
xAI shipped Build Mode on July 28, 2026 in a dated article of its own, not in the release notes. Easy to miss if the release notes are how you track Build. Check how it behaves with plan mode and with the permissions you’ve already set before you write a workflow around it.
- A dated first-party release, not a release note
- Confirm its current behavior in the product
- Re-test any Build workflow written before July 28
Workflows July 23
Workflows in Grok Build shipped on July 23, 2026, also in its own dated article. It belongs in the same inventory as /goal, plugins and, since September, memory. That inventory is the list of things a Build installation can start, carry or remember without anyone typing the next prompt.
- Dated July 23, 2026
- Inventory it alongside /goal, plugins and memory
- Decide who may create and share one
Grok Build API grok-build-0.1
A public-beta API path lets developers wire the coding model into their own workflows. Both the model and the price are published this time, which isn’t something you can take for granted here.
- Model ID
grok-build-0.1, the replacement xAI named forgrok-code-fast-1in the May 15 retirements - Listed at $1.00 input, $0.20 cached input and $2.00 output per 1M tokens at short context, $2.00, $0.40 and $4.00 at long context, with a 256k window: unconfirmed as of October 15, 2026
- Beta stability: evaluate and instrument before you depend on it
Implement organization-wide audit logging for authentication changes. Follow existing architecture, add migration-safe storage, update API and admin UI, write abuse-case tests, and finish only when all checks pass.
Inspect this repository for the highest-risk authentication and authorization flaws. Don’t change code yet. Rank findings by exploitability and show the exact evidence behind each one.
Split this migration into independent workstreams that can run safely in parallel. Identify shared files, sequencing constraints and the final integration test before dispatching sessions.
Report only: files changed, user-visible behavior, tests run, security implications, unresolved issues and the exact review I should perform before merge.
Use X as a sensor, not a source of universal truth
X will tell you what people are saying faster than anything else. It will also tell you what bots are saying, what campaigns are pushing and what a confident stranger got wrong. Same feed, right? So treat it as a sensor and not as a source. Since August 29 Grok Bot works with X directly, which puts an agent on that same surface.
Narrative emergence
See which explanations and phrases are spreading before they reach formal analysis.
Real-time sentiment
Track reaction to products, earnings, policy and events while people are still arguing about them.
Practitioner commentary
Find the engineers, researchers, operators and witnesses closest to an event.
Attention dynamics
See who is amplifying a claim and how fast it moves through communities.
Not representative
X users and visible posts aren’t a census of your customers, voters or professionals.
Coordinated activity
Bots, incentives and campaigns can manufacture the look of consensus or urgency.
Primary records still win
Use releases, filings, transcripts, source data and direct evidence for factual claims.
Recency decays quickly
Capture the date and time, because a real-time answer can go stale within hours.
Image, video, speech and audio are becoming one creative stack
One pass now gives you motion, physics, ambience, sound effects and speech. Imagine Video 1.5 does all of it together, and it gained a References release on July 31, 2026. The image side moved to 2.0 on August 7, 2026, then took an API update on August 28. Faster experiments, yes, but a single clip can now fail in four ways at once. Four lifecycle facts belong in a calendar. The model grok-voice-transcribe-1.0 reached end of life on October 2, 2026, and its requests now run on 2.0. The alias grok-voice-latest moved to grok-voice-3.0 on October 14. The model grok-voice-2.0 was deprecated the same day, with no end date. And grok-imagine-image-quality retires on November 2, 2026.
Imagine image API, August 28 Parameter change
A changed default is a silent change in what comes out. The August 28, 2026 release notes add an auto quality parameter on grok-imagine-image-2.0 and move the default from medium to auto. Editing now takes up to 5 source images, up from 3, and two aspect ratios were added: “21:9 (cinematic widescreen) and 5:2 (wide banners).” Re-run your reference prompts. Don’t assume parity.
- Default moved from medium to auto
- Up to 5 source images for editing, up from 3
- New 21:9 and 5:2 aspect ratios
Grok Imagine Image Quality Retires November 2
The dedicated quality endpoint stops being its own model on November 2, 2026. Requests keep working. They just get served by grok-imagine-image-2.0 with quality set to low, a cent cheaper per image at every resolution. Cheaper output at lower quality with no error is the kind of change that reaches a brand review before it reaches an engineer.
- Quality tier until November 2: $0.05 at 1K, $0.06 at 1.5K, $0.07 at 2K. Low quality on 2.0: $0.04, $0.05, $0.06
- Medium on 2.0: $0.06, $0.07, $0.08, a cent more than the quality tier
- Migrate deliberately rather than being migrated
- Set the quality parameter explicitly on 2.0
- Add a visual regression check before November 2, 2026
Grok Voice 3.0 October 14 · behind grok-voice-latest
The new speech-to-speech model, out October 14, 2026, and already running under you if you call the alias. The alias grok-voice-latest points to grok-voice-3.0, and xAI says agents on the alias were switched over automatically with no changes needed. The price didn’t move: $0.08 per minute, or $4.80 an hour, plus $0.004 per text input. The API didn’t move either. xAI says 3.0 uses the same endpoint, session parameters and events as 2.0. So the upgrade costs nothing and changes the voice your customers hear. Test it on your own calls before you assume the scripts still land.
- ID
grok-voice-3.0, $0.08 per minute plus $0.004 per text input - Same endpoint, session parameters and events as 2.0, per xAI
- xAI calls it the world’s most intelligent speech-to-speech model and cites a score of 86.9 on Artificial Analysis’s Speech-to-Speech Index: vendor claims
- xAI says Starlink call centers handle 20,000 calls a day, roughly 70 percent with no human in the loop: vendor self-report
- No model card on
x.ai/safety
Grok Voice 2.0 Deprecated October 14 · no end date
Announced July 29, 2026, served by the alias from August 5, and deprecated on October 14, 2026. No end-of-life date. The price table labels the row Deprecated, and the model page now calls it a previous-generation model. xAI’s instruction is short: if you pin grok-voice-2.0, set the model to grok-voice-3.0. The last undated xAI voice deprecation, Transcribe 1.0, ended 14 days after it was announced. Plan on that clock, not on the missing date.
- $0.08 per minute plus $0.004 per text input, the same as 3.0
- Deprecated October 14, 2026, no end date published
- The July 29 article now names this model
grok-voice-2.0and no longer uses the Think Fast name - Move pinned calls to
grok-voice-3.0on your schedule, before xAI sets one
Grok Voice Think Fast 1.0 Removed, not deprecated
The model before Grok Voice 2.0, and a good lesson in reading a page twice. On September 3, 2026 the docs marked it [Deprecated] at $0.05 per minute of audio, with the same $0.004 per text input. That read like a rate you could still get by naming the version. It isn’t one. On October 15, 2026 grok-voice-think-fast-1.0 has no row on the price table and no deprecation marking. Its model page still renders by that ID: modalities text and audio, region us-east-1, and a Pricing heading with nothing beneath it. The page x.ai/voice still names Grok Voice Think Fast 1.0 in a benchmark chart. Meanwhile the July 29 article now calls the same predecessor plain Grok Voice 1.0. Whether that’s a rename, and whether the ID still answers, no page says. Stop planning on $0.05.
- Gone from the price table with no dated retirement notice
- No longer marked [Deprecated] anywhere
- Model page renders with an empty Pricing section, which is not a rate
- Still callable or not: unresolved
- Budget at the $0.08 rate and migrate to
grok-voice-3.0deliberately
Grok Voice Transcribe 2.0 Default · 1.0 ended October 2
This one’s done, and it went faster than the wording suggested. On September 18, 2026 xAI said 2.0 would become the default in the Speech-to-Text API and 1.0 would be deprecated in the coming weeks. No date. Then grok-voice-transcribe-1.0 reached end of life on October 2, 2026, fourteen days later, and its requests now route to 2.0 at the same price. 2.0 is the default when you leave the model out. Here’s the trap. The September 18 article still says you can pin 1.0 during the transition. The live docs say the transition is over. The live page governs the present, so a pin to 1.0 now lands on 2.0. If your pipeline was tuned to 1.0 output, it has been running on 2.0 since October 2. Check the transcripts, not the config.
- $0.10 per hour batch, $0.20 per hour streaming, diarization, timestamps and key terms included
grok-voice-transcribe-1.0reached end of life on October 2, 2026; requests route to 2.0 at the same price- 2.0 is the default when
modelis omitted - The speech-to-text docs no longer mention 1.0
- Compare transcripts from before and after October 2, 2026 on your own audio
Imagine Video 1.5 June 16
Better motion, better physics, synchronized audio and clearer speech. Released June 16, 2026, then extended by Imagine Video 1.5 with References on July 31, 2026. xAI describes making videos from text or image references with preset voices, up to 1080p.
- Quality and Fast modes
- References release dated July 31, 2026
- Product and API access
- Library search for generated media
Documented video resolutions and rates
xAI describes Imagine Video 1.5 output up to 1080p. The price table lists grok-imagine-video at $0.05 per second at 480p and $0.07 per second at 720p, with no 1080p row for it.
- At the listed rate, six seconds of 720p is $0.42 of generation
- A lite tier,
grok-imagine-video-1.5-lite, lists $0.02, $0.03 and $0.14 per second at 480p, 720p and 1080p, and no release note dates it - Choose the resolution the channel needs
- A living docs page, so re-check the rates before you budget
Video 1.5 Fast
Six-second 720p clips in about 25 seconds, according to xAI.
- Rapid iteration
- Useful for social and concepts
- Inspect every clip for sync and warping
Audio and speech
Sound effects, ambience and dialogue come out with the video instead of arriving as a separate first pass.
- Faster concepting
- Voice and brand risk
- Still needs final sound review
Imagine Image 2.0 August 7
The image side moved to version 2.0 on August 7, 2026 and gained new parameters on August 28. New version, new output. Re-test any prompt library or brand guardrail you built against the old one before you assume the pictures still match.
- New version, new output characteristics
- Re-run your reference prompts
- Re-check text, likeness and product truth
Voice APIs
xAI offers speech-to-text, text-to-speech, voice-agent tools and custom voice work, and shipped 21 new flagship Grok voices on July 6, 2026. The Voice Agent Builder is still marked Beta.
- Multilingual workflows
- 21 flagship voices since July 6, 2026
- Consent and impersonation controls
- Secure voice assets
Grok moved into Microsoft 365 and Google Workspace
The add-in program started in June. Grok for PowerPoint shipped on June 16, 2026 and Grok for Word on June 18. Then Excel on July 20, Outlook on July 21 and Google Workspace on July 24. Grok now sits beside the documents your teams already work in, on surfaces Microsoft and Google own. Since August it also sits inside those companies’ model catalogs and inside GitHub Copilot. And since September 18, 2026, by Microsoft’s account, a second, completely separate mechanism reaches Word, Excel and PowerPoint, this one run by Microsoft through its Frontier Program. Keep the two apart, because they share nothing but the app names. Treat all of it as a distribution decision, not just a feature release.
Grok for PowerPoint June 16
The first add-in in the program, out on June 16, 2026, about a month before the Excel, Outlook and Workspace releases. An add-in policy should date the program from here.
- The add-in program starts here
- Confirm the tenant add-in policy before any rollout
- Review what the add-in may read from a deck
Grok for Word June 18
Two days later, on June 18, 2026, drafting and revision arrived beside the open document.
- Second in the program, ahead of Excel
- Drafting and revision beside the open document
- Review connector scope with your Microsoft 365 admin
Grok for Excel July 20
A free Microsoft 365 add-in. Ask a spreadsheet questions in plain English, get formulas back, and run scenarios and forecasts against the open workbook.
- Plain-English queries over your data
- Formula generation and scenario runs
- Connectors for SharePoint, Drive and email
Grok for Outlook July 21
Thread summaries, reply drafts matched to how you write, and inbox triage inside Outlook. Who is entitled to it is still unconfirmed. Since October 12, 2026 The X Subscription folds X Premium into the Grok plans, but the plan copy doesn’t say which tier includes the Outlook add-in. So the common claim that every paid X and SuperGrok user gets it has no first-party support.
- Entitlement unconfirmed: ask which X Subscription tier includes it
- Style-matched draft replies
- Review drafts before sending, because the tone is imitated rather than verified
Grok in Google Workspace July 24
One free add-on from the Google Workspace Marketplace that puts Grok beside the open file in Sheets, Slides and Docs.
- A single add-on covers all three apps
- Installed through the Marketplace
- Confirm your admin allows Marketplace installs
Two separate routes reach Word, Excel and PowerPoint Two routes
Same three Office apps. Two mechanisms that share nothing but the app names. The first is xAI’s own: free add-ins dated June 16 to July 24, 2026, installed from the Microsoft 365 and Google Workspace marketplaces and governed by your tenant add-in policy. The second is Microsoft’s. Grok reaches Word, Excel and PowerPoint through the Microsoft Frontier Program, behind a dedicated admin setting that’s off by default, under Microsoft’s Product Terms and DPA. Frontier customers in the European Union, the European Free Trade Association and the United Kingdom are excluded, and so are government and sovereign clouds, with no end date given. Different owner. Different gate. Different regional terms. Same app names, right? And only one of the two is closed to European users. A policy written about one of them doesn’t cover the other, and anyone who merges them gets both the gate and the geography wrong. Copilot Studio is a third route again, with xAI as an independent processor under its own terms.
- xAI add-ins: June 16 to July 24, 2026, marketplace install, tenant add-in policy
- Frontier Program: available since September 18, 2026 per Microsoft, a Microsoft admin setting that’s disabled by default
- Only the Frontier route carries the EU, EFTA, UK, government cloud and sovereign cloud exclusion, and it has no published end date
- Ask which of the two a team means before you approve or forbid it
- Source for the Frontier route: Microsoft Learn, “SpaceXAI as a subprocessor in Microsoft Online Services.” No xAI page mentions it
Grok inside the rival catalogs June to August
Grok 4.6 has been in GitHub Copilot since August 14, 2026, Amazon Bedrock since August 19, the Gemini Enterprise Agent Platform since August 21 and Microsoft Foundry since August 26. Grok has been on Databricks since June 18, 2026 and on Bedrock since June 17. Add-ins put Grok next to the documents. Catalog listings put it inside the platform contract. Either route can bring Grok into a company without a decision from whoever owns AI policy.
- Four surfaces carried Grok 4.6 in twelve days, and two catalogs carried Grok from June
- Procurement may already permit it
- Decide the policy before a team discovers the listing
Automations July 16
Grok can run recurring tasks on its own, on a schedule or from an email trigger. Every run opens as a full conversation thread you can read afterward.
- Scheduled automations for all users
- Email triggers were SuperGrok-only at launch: ask which X Subscription tier carries them now
- Every run leaves an inspectable thread
Automations, Routines and /goal are three different things Clarification
Three scheduling concepts. Three surfaces. Three owners, and three very different blast radii. Automations is the consumer feature for recurring tasks, on a schedule or an email trigger. The /goal command is the long-running execution mode inside the Grok Build CLI. Routines are the third. xAI introduced them in its September 3, 2026 post on designing Grok Bot, which describes them as giving a Bot a standing responsibility that runs on a schedule or in response to an event. A policy document that says only “scheduled tasks” now covers none of them properly.
- Automations: recurring, consumer, scheduled or email-triggered
- Routines: a standing responsibility held by a Grok Bot, scheduled or event-driven
- The
/goalcommand: sustained engineering execution in the CLI - Name the one you mean and don’t substitute one for another in a plan
Why this matters Strategic
Shipping into Excel, Outlook, Sheets, Slides and Docs puts Grok on the incumbents’ own ground, where Microsoft and Google ship their own assistants. Adoption can now happen with nobody making a purchasing decision.
- Expect overlap with Copilot and Gemini entitlements
- Set an add-in approval policy before demand arrives
- Audit which connectors each add-in requests
Grok’s enterprise story now extends beyond X
xAI rebuilt x.ai/pricing on October 12, 2026 around The X Subscription, and the business tier now has two names. The page lists Free at $0, Plus at $8, Premium at $30, Super at $100, Ultra at $200, Teams at $30 and up per user per month, and Enterprise at Custom. The page x.ai/grok/business sells Business at $30 per user and never mentions Teams. A $59 figure on x.ai/enterprise is boilerplate that never mentions Grok, so don’t quote it. SOC 2 is gone from the pricing page and now sits on the Business page. Then there’s retention: your API traffic is stored for 30 days by default, and turning that off costs you features. Three questions before anyone signs, right?
| Tier | Published price | What xAI says it adds |
|---|---|---|
| Free | $0 per month | Entry tier on x.ai/pricing |
| Plus | $8 per month | More usage in Grok and Cursor, an X checkmark, creator tools, fewer ads on X; lists Grok Chat, Voice, Imagine and Build |
| Premium | $30 per month, marked Most popular | The benefits of SuperGrok, Cursor Pro and X Premium+; 4x Plus usage |
| Super | $100 per month | 15x Plus usage |
| Ultra | $200 per month | 50x Plus usage |
| Teams | $30+ per user per month | SSO, admin controls, consolidated billing, usage analytics and SOC 2 compliance |
| Enterprise | Custom, Contact Sales | Grok and Cursor from one dashboard with one usage pool; invoice and wire billing |
| Business | $30 per month per user, on x.ai/grok/business only | Not listed on x.ai/pricing; the Business page lists no Teams tier |
| Capability | Business | Enterprise | Vault (add-on to Enterprise) |
|---|---|---|---|
| Team management and billing | Included | Included | Included |
| Google Drive grounding | Permission-aware | Permission-aware | Permission-aware |
| SSO and SCIM | Page badge on x.ai/grok/business; tier not stated | Included | Included |
| Advanced audit and security | Standard controls | Advanced | Advanced |
| Dedicated data plane | Not included | Optional add-on | Included |
| Customer-managed keys | Not included | Optional add-on | Included |
| SOC 2 (Type I and II) | Listed on x.ai/grok/business | Not stated per tier | Not stated per tier |
The X Subscription October 12 · one plan, four products
One subscription now covers Grok, Grok Bot, Cursor and X Premium. That changes who in your company is already paying for Grok. Premium at $30 carries what xAI calls the benefits of SuperGrok, Cursor Pro and X Premium+, previously $90 a month combined. Usage is sold in multiples of Plus: Premium 4x, Super 15x, Ultra 50x, from a pool that refreshes weekly. API use bills separately and doesn’t draw from that pool. Invoice and wire billing need Enterprise. Team users get Premium, Super and Ultra at the same per-seat prices as the individual plans. SuperGrok Lite, SuperGrok Heavy and Business are gone from the pricing page. Existing SuperGrok, Cursor and X Premium subscribers keep what they have, and switching is rolling out with a prorated refund and no date. Cursor’s help says the switch is permanent. Cursor’s pricing page names the seller too: “Subscriptions are only sold directly through X Subscription Corp.” So an expense line reading SuperGrok and one reading Premium might be the same product. Or not. Find out before renewal.
- Free $0, Plus $8, Premium $30, Super $100, Ultra $200, Teams $30+ per user, Enterprise custom
- Usage in multiples of Plus: 4x, 15x and 50x, refreshed weekly
- API billed separately from the plan pool
- Invoice and wire billing require Enterprise
- xAI says it authorizes no resellers or third-party sellers
- Cursor’s pricing page names X Subscription Corp as the only seller
- xAI says each new tier gives more usage per dollar than the plan it replaces: a vendor claim
- Switching for existing subscribers: rolling out, no date, and permanent according to Cursor’s help
- Whether the SuperGrok tiers can still be bought new: no page says
A first-party page is serving an Enterprise figure that isn’t a price $59 · not a Grok price
On October 15, 2026 x.ai/enterprise carries a heading reading For Enterprise, a section headed About the Enterprise Plan, and a figure rendered as $59 per user per month. Meanwhile x.ai/pricing lists Enterprise as Custom with a Contact Sales button. A buyer will find that figure on a live x.ai path, and it must not be quoted as a Grok Enterprise price. The same page shows placeholder values throughout. It claims your company could save 0 hours a month per person, $0 in savings and 0 percent return. And its feature copy talks about calendars, Slack and scheduling assistants named Amy and Andrew. Grok isn’t mentioned once. It reads as template or staging content served on a live x.ai path. If a vendor conversation or an internal business case cites the figure, ask for the number in writing on paper that xAI will stand behind.
Zero data retention, 30 days by default, and a residency hole Procurement
By default xAI stores every API request and response on its servers, encrypted at rest, for 30 days, for auditing. xAI says it never trains on your API inputs or outputs without explicit permission. You can turn storage off with zero data retention, and xAI now names the cost: it disables features that rely on stored data, such as the Batch API and Files. xAI’s own FAQ says that for most customers it doesn’t recommend ZDR. Then there’s the part a residency clause can trip over. The US regional endpoint at us.api.x.ai leaves out Files, Collections and network paths, and server-side tools too: web search, X search and code execution may process data outside the United States. It serves only grok-4.7 and grok-4.6, with no image, video or voice APIs. xAI says it plainly: a regional endpoint isn’t, by itself, a comprehensive data-residency guarantee. So a contract that says US-only can be true of the model call and false of the search it ran. Ask about all four by name.
- API requests and responses stored encrypted for 30 days by default
- Zero data retention disables the Batch API, Files and other features that rely on stored data
- xAI states it does not train on API inputs or outputs without explicit permission
- The US endpoint excludes Files, Collections, network paths and server-side tools
- The US endpoint serves
grok-4.7andgrok-4.6only, with no image, video or voice APIs - All of this lives on developer pages rewritten in place, so confirm it in a contract
Company knowledge
Grok can search Google Drive while respecting the permissions already set there.
- Citation previews
- Highlighted relevant passages
- No access to unshared files
Data commitment
xAI says business data isn’t used to train its models.
- Still review product terms
- Map regional data needs
- Control connector access
Collections API
Agentic search across large document stores, for data rooms, legal review and financial modeling.
- Curate the source set
- Check retrieval coverage
- Preserve citations
Enterprise controls
SSO, SCIM, administration and audit features for larger managed deployments.
- Lifecycle users correctly
- Assign product ownership
- Monitor usage
Vault Add-on, not a tier
An isolated data plane with application-level encryption and customer-managed keys, aimed at the most sensitive customers. Write down what it isn’t. Vault isn’t one of the tiers on the pricing page, which since October 12, 2026 are Free, Plus, Premium, Super, Ultra, Teams and Enterprise. Treat it, and the dedicated data plane and customer-managed keys beside it in the table above, as options layered on Enterprise. Not as another plan to buy.
- Not one of the published plan tiers
- An option on top of Enterprise, priced through sales like Enterprise itself
- Evaluate operational model, logging and recovery
- Verify contractual scope in writing
Third-party safeguards evaluation September 1
A lab tested Grok 4.6 and got two numbers that pull against each other by design. LatchBio measured 59.2% refusal on adversarial tasks and 64.8% completion on legitimate ones. Those figures are LatchBio’s, published by xAI. It’s a safeguards check, not a product change. Refusing more bad requests and completing more good ones fight each other, so read the pair together and never one alone.
- Source: “Biosecurity at the frontier,” xAI, September 1, 2026
- Figures produced by LatchBio, published by xAI
- A safeguards study, not a capability or product release
- Useful evidence for a security review, not a compliance certificate
Skills and apps
Reusable work behavior and connected tools turn the product into a workflow layer for the organization.
- Govern creation and sharing
- Review third-party connectors
- Retire stale skills
SOC 2 moved off the pricing page Compliance
The pricing page no longer names a single certification. Its footer links to a BAA, a DPA, a subprocessor list, a security page and a privacy portal, and that’s it. SOC 2 now lives on three other xAI surfaces, and they don’t say the same thing. The page x.ai/grok/business lists SOC 2 Type I and II for Business and carries header badges for SOC 2 Type II, HIPAA, GDPR and CCPA, and SSO and SCIM. The X Subscription article says Teams includes SOC 2 compliance. The developer security FAQ says xAI is SOC 2 Type 2 compliant, asks a GDPR question in a heading and answers it with SOC 2, routes HIPAA to a BAA questionnaire, and points customers under NDA to a Trust Center. A badge isn’t a position. The HIPAA badge doesn’t say which plans qualify or whether a BAA is required. Ask for the report and the signed BAA, not the badge. The safety page separately links an xAI Frontier AI Framework dated June 30, 2026. That’s a policy document, not an attestation, so don’t hand it to a reviewer as one.
x.ai/pricing: no certification named; footer links to BAA, DPA, Subprocessors, Security and Privacy Portalx.ai/grok/business: SOC 2 Type I and II, plus SOC 2 Type II, HIPAA, GDPR and CCPA, and SSO and SCIM badges- Developer security FAQ: SOC 2 Type 2, a GDPR heading answered with SOC 2, a BAA questionnaire for HIPAA, a Trust Center under NDA
- ISO 27001 and FedRAMP aren’t among the badges
- All three change without notice, so confirm directly
Three price levers that move the bill API commercials
The headline $2 and $6 isn’t the whole bill. Three switches sit behind it, and two of them push the number up. The docs price page lists a US regional endpoint at 1.1 times standard rates and Priority Processing at 2 times standard rates. The Batch API is the one that pulls down, and it’s narrower than it sounds. It takes 20 percent off grok-4.3 and three grok-4.20 models, nothing off image or video, and the flagship can’t use it at all. So the cheapest way to run xAI’s best model is the full-price way. Regions don’t line up either. Model pages have stated us-east-1, but the grok-imagine-video-1.5-lite page lists us-east-1 and us-west-2, and the regions page links a console view for us-central-1. Before you sign off a budget, find out which levers a team has switched on and which region it’s actually hitting.
- US regional endpoint: 1.1x standard rates
- Priority Processing: 2x standard rates
- Batch API: 20 percent off
grok-4.3,grok-4.20-0309-reasoning,grok-4.20-0309-non-reasoningandgrok-4.20-multi-agent-0309only; no discount on other models, and none ongrok-4.7 - The
grok-imagine-video-1.5-litepage marks Batch as supported with batch pricing N/A - Ask xAI which region is the contractual answer
- Read from docs pages rewritten in place, so confirm directly
Grok Bot for Enterprise September 3
xAI says enterprises need to govern Bots at scale, and that this release adds the access, network and audit controls to do it. Its isolation claim has two halves. Each user’s work in Grok Bot runs in its own secure, isolated environment, separate from every other user. And a Bot has no access by default, reaching only the accounts you sign it into. xAI names Legora, Supermicro and ServiceTitan as customers and says thousands of organizations have adopted Grok Bot since launch. All of that is vendor statement, not audited finding. The post also offered free usage for two weeks from September 3. That expired on September 17, 2026, and no price is stated for the period after it.
- Access, network and audit controls, as described by xAI
- Isolation and adoption figures are vendor claims, not findings
- The free-usage offer expired on September 17, 2026
- A full security architecture document is linked from the post, and the isolation claim rests on it rather than on the post
- Read that document before relying on the isolation claim
Both case studies are xAI measuring itself Vendor self-report
There are two of them now, and neither has a third party in it. On September 4, 2026 xAI pointed Grok Bot at its own vendor spend and published more than $100,000 in direct savings. On September 22 it published its own support desk numbers: a 175 percent rise in tickets absorbed with zero new hires, roughly 200 employees not hired, and cost per resolution of $0.20 to $0.30 against a stated industry range of $1 to $4. Read both the way you read the LatchBio figures, then one notch more carefully. The vendor ran the study, on its own data, and published its own result. Useful descriptions of a workflow. Not evidence of what the same agent would do in your company.
- Procurement, September 4, 2026: $14,220 from 43 unused SaaS seats, $85,662 annually in unused SKUs, an office supply order cut from $14,629 to $6,143
- Customer support, September 22, 2026: trained on over one million customer interactions, 99 percent of refund requests resolved without a human
- xAI’s own data, xAI’s own measurement, xAI’s own publication, both times
- No independent verification of any line item
- Useful as a workflow template, not as a savings forecast
- Any pilot should establish its own baseline before it starts
Nine habits for using Grok without confusing speed with truth
Grok pays off when a team keeps four things apart on purpose: live signal, verified evidence, blunt critique and bounded execution. And when nothing you ship leans on a moving alias, an undated absence claim, or a model that can walk off a price table without notice.
Use X for signal
Map the reaction and the language. Don’t call it representative truth.
Verify the factual core
Move every claim that matters to a primary record.
Time-stamp live answers
Say when the signal was observed, because it will change.
Ask for direct critique
Use Grok’s tone to stress-test an idea, then go back to the evidence.
Use /goal for outcomes
Give Build a finish line, tests and a boundary on what it may do.
Inspect external state
Look at the code, the file, the post or the media. Not the claim that it’s done.
Folders fail, files resolve
On xAI, a bare directory path can fail to load while the pages inside it resolve. The host data.x.ai does it with model cards. The path docs.x.ai/developers/migration does it with the retirement guides. Both read as a dead section. Before anyone says xAI dropped a document, open the document’s own link.
Name region, surface and date
API, consumer app, cloud catalog and geography are four separate claims, and they landed on four different days.
Pin the model ID, and know a pin can expire
Never ride an alias or a default. The alias grok-voice-latest moved on August 5 and again on October 14, 2026, with no action by the customer. The model grok-imagine-image-quality silently drops to low quality on November 2, 2026. And a pin isn’t forever. A pin to grok-voice-transcribe-1.0 has landed on 2.0 since October 2, 2026.
Fast social intelligence is noisy by construction
The things that make Grok good are the same things that make it risky. Live feeds can be gamed. A confident tone can hide uncertainty. And an integrated agent can act before a weak claim gets corrected. Two more risks sit on xAI’s own pages. A bare directory path can fail to load while every page inside it resolves, which makes an absence easy to assert and hard to prove. And xAI rewrites undated pages without notice, in every direction: a price gets reconciled upward, a model vanishes from the price table with no retirement date, and a flagship gets replaced on a page that looks identical the next morning.
Selection bias
Visible X conversation isn’t the same thing as broad public, customer or employee sentiment.
Coordinated manipulation
Bots and campaigns can manufacture salience, repetition and the look of consensus.
Confident tone
Directness can make an uncertain reading feel settled. Ask for sources and calibration.
A bare xAI directory fails while every page inside it resolves
xAI does this in two places, and it reads like a dead section both times. The paths data.x.ai/ and data.x.ai/model-cards failed to load on October 15, 2026, while three model card files beneath them are live at their URLs. The paths docs.x.ai/developers/migration and docs.x.ai/developers/deprecations failed to load the same day, while the retirement guides at docs.x.ai/developers/migration/may-15-retirement and docs.x.ai/developers/migration/imagine-image-quality-nov-2 both resolve and are linked from the models page. So a check aimed at a folder reports the contents as gone. A dead folder link says nothing about the documents inside it.
Model cards are per model, and they sit on two hosts
Six cards exist. Grok 4.7 (September 21, 2026, revision 2026-09-21), Grok 4.6 (August 12, 2026, revision 2026-08-17) and Grok 4.5 are on media.x.ai. Grok 4 Fast, Grok Code Fast 1 and Grok 4 are on data.x.ai. All six are text models. There’s no card for any voice model, for grok-build-0.1 or for any Imagine model. A card for the current model says nothing about the one you deployed in July. Match the card to the model ID your product calls.
A priced model with no ID to call
The page x.ai/api carried three different flagships inside four weeks. First grok-4.3 at $1.25/$2.50 in early September, then grok-4.6 at $2.00 and $6.00, and by October 1, 2026 grok-4.7, with grok-4.6 pricing gone. xAI changes that page with no notice and no date, so a figure copied from it two weeks earlier is quietly wrong. The live hazard is Grok 4.7 Fast. It now has a price, $4 / $1 / $12 below 200,000 tokens and $6 / $1.50 / $18 above, and still no model ID. It runs only in Cursor and Grok Build, billed through the plan. Don’t budget for a model you can’t name. And if a vendor conversation quotes “twice the price,” point out it’s 1.5x on long context, and ask for the ID.
Two live pages, two names for the team tier
xAI’s pricing page, x.ai/pricing, rebuilt on October 12, 2026, lists Teams at $30 and up per user per month and no Business tier. The page x.ai/grok/business lists Business at $30 per user per month, plus Enterprise, and no Teams tier. xAI’s Grok Bot docs list Individuals, Teams and Enterprise, and Business doesn’t appear. Team Bots is sold on Teams and Enterprise plans. So a buyer can be quoted Teams by one xAI page and Business by another, at the same price, with nothing on either page saying they’re the same thing. Ask which tier the order form names, and what happens to the other one at renewal.
A silent quality downgrade has a date
On November 2, 2026, 18 days after October 15, grok-imagine-image-quality retires and its requests get served by grok-imagine-image-2.0 at low quality, a cent cheaper per image at every resolution. No error. No outage. Cheaper invoice, worse images. Put a visual check and a decision in the calendar before the date, because nothing will alert you on the day.
An undated deprecation can end in two weeks
On September 18, 2026 xAI said Grok Voice Transcribe 1.0 would be deprecated in the coming weeks. No date. It reached end of life on October 2, 2026, fourteen days later, and its requests now route to 2.0. The pin xAI offered for the transition stopped pinning anything that day. Now the same shape is back. The model grok-voice-2.0 was deprecated on October 14, 2026, with no end date. Treat an undated xAI deprecation as a two-week clock, because the last one was. Move pinned voice calls to grok-voice-3.0 before xAI picks the day for you.
Voice alias moved twice
On August 5, 2026 grok-voice-latest began serving Grok Voice 2.0. That’s 60 percent more per minute of audio, $0.05 to $0.08, with nobody on your side doing anything. On October 14, 2026 it moved again, to grok-voice-3.0, at the same $0.08. The August warning was published a week ahead and it landed on the day, which is the argument for keeping a watchlist. The October move came with the launch itself. A watchlist only catches what the vendor dates.
A model can leave a page with no notice at all
In early September grok-voice-think-fast-1.0 was marked [Deprecated] at $0.05 per minute of audio. On October 15, 2026 it’s still absent from the price table. No deprecation marking. No retirement date. No dated article. Its model page renders, and the Pricing heading on it has nothing underneath. A dated deprecation is something you can put on a calendar, raise a change request against and argue about with a vendor. A silent removal is none of those. It looks tidier on the page and it’s strictly worse for you. Treat any model that disappears from a vendor price table as a migration you’ve already started, whether or not it still answers when you call it.
Don’t count anything on the news index
The x.ai/news index has served different totals on the same day and left out articles that resolve at their own URLs, including xai-joins-spacex and anthropic-compute-partnership. On October 15, 2026 it listed 87 entries, both of those among them. That’s one quiet day, not a fix. An index whose count can move within a day can’t support a count, and it can’t support a claim that something wasn’t published. Never enumerate xAI releases from it. Link the dated article instead.
Beta language is sticky
Grok Bot went from three plans to eight on August 26, 2026, gained an X integration on August 29 and gained enterprise access, network and audit controls on September 3. None of those posts uses the word beta, and none says it left beta either. Then on September 28, forty-eight days after launch, xAI shipped Team Bots and wrote public beta in plain words. So the beta label is still live on the product line, even with governance controls and a thousands-of-organizations adoption claim attached. On October 15, 2026, 65 days after the August 11 launch, the Grok Bot docs carry no beta or GA label at all, and the Team Bots article still says public beta. Widen the availability claim to the named plans. Stop short of calling it generally available, because xAI hasn’t.
Regional and tier availability, and why the EU isn’t settled
Grok 4.5 launched without EU access and gained it on July 17, 2026 on xAI’s own API console. That date covers one surface only. Availability varies by surface. GitHub Copilot, Amazon Bedrock, the Gemini Enterprise Agent Platform, Microsoft Foundry and Databricks each carry their own regions and terms, and Copilot access may need enabling in Copilot settings on business and enterprise tenants. One surface is shut to European users outright. Microsoft says Grok has been available in Word, Excel and PowerPoint to eligible Frontier Program customers since September 18, 2026, behind an admin setting disabled by default. Customers in the European Union, the European Free Trade Association and the United Kingdom are excluded, and so are government clouds (GCC, GCC High and DoD) and sovereign clouds, with no end date given. Those models also sit outside Microsoft’s in-country processing commitments. That rests on Microsoft’s own Learn page. No xAI page mentions it. And it isn’t the xAI Frontier AI Framework, a safety policy dated June 30, 2026 with no Microsoft content in it. Copilot Studio is narrower still: Microsoft lists Grok there for the United States only. xAI’s own regions don’t line up either. Model pages have stated us-east-1, the grok-imagine-video-1.5-lite page lists us-east-1 and us-west-2, and status.x.ai publishes no region list in text. Treat any region list as a question for xAI rather than an entitlement. Check the current status per surface, per model and per tier. Not a remembered one.
Third-party evaluation isn’t certification, and self-reporting isn’t evaluation
The LatchBio evaluation xAI published on September 1, 2026 reports 59.2% refusal on adversarial tasks and 64.8% completion on legitimate ones for Grok 4.6. Those are LatchBio’s measurements on task sets somebody chose, published by the vendor whose model was tested. Two case studies are a further step away from independence. On September 4, 2026 xAI ran Grok Bot against its own vendor spend and published its own savings. On September 22 it published its own support desk figures the same way. Cite all three with their attributions. Present none of them as an approval or a forecast.
Agent permissions
Build plugins, external integrations and business apps widen the blast radius of a mistake, and Grok Build has been on web and mobile since August 19, 2026.
Voice and likeness
Custom voices and generated speech need explicit consent, impersonation controls and secure handling of the assets.
Integrated media errors
Video, physics, speech and audio can each fail on their own inside one polished clip. And changed defaults, like the August 28 move from medium to auto quality, shift the output without you doing anything.
Agent memory is now a security scope
Since September 16, 2026 Grok Build writes what xAI calls conventions, decisions and project facts to markdown files that live across sessions, per project workspace and globally. xAI says task state, temporary conclusions and secrets are deliberately left out. Take that as design intent, not as an assurance you’ve tested. An agent that carries notes between sessions hands you three new things. A new place for sensitive detail to land. A new artifact that travels with a repository. And a new thing to review when somebody leaves the team. Read the stored files with /memory, and decide who is allowed to.
Three cutoffs for one model
Grok 4.7’s knowledge cutoff reads May 2026 on the docs model reference. The model card says a pretraining cutoff of June 2026, with supplemental data as late as August 2026. The dedicated 4.7 model page says nothing at all. Three months of spread, three first-party pages, no reconciliation. The May date sits on the index page everybody opens first, which is exactly why it gets quoted as settled. Name the surface whenever you state a cutoff. And never let a recency assumption ride on a number xAI’s own pages disagree about.
The retirement list is readable, and it names eight models
xAI’s migration guide for May 15, 2026, last updated September 2, lists eight models switched off at 12:00 PM Pacific that day. The models grok-4-1-fast-reasoning, grok-4-1-fast-non-reasoning, grok-4-fast-reasoning, grok-4-fast-non-reasoning and grok-4-0709 all went to grok-4.3 at various reasoning efforts. And grok-3 went to grok-4.3 with reasoning effort none. Then grok-code-fast-1 went to grok-build-0.1. Last, grok-imagine-image-pro went to grok-imagine-image-quality, which is itself retiring on November 2, and xAI says pro requests will follow that second redirect too. Read that last chain twice. A replacement model can be retired before you’ve finished migrating onto it. xAI’s migration guide lives at a child path, and the folder above it failed to load on October 15, 2026.
Rapid product churn
The release cadence is why dated claims and direct source links aren’t optional here.
Where these facts come from
Each entry below is a dated article, a model card, an xAI migration guide, or a live vendor page that is the only authoritative record of its fact. None is the rolling news index. SpaceX acquired xAI on February 2, 2026. Page titles now render “SpaceXSI,” the footer reads “© 2026 SpaceXAI LLC,” Microsoft says SpaceXAI, and no xAI page explains or dates the SpaceXSI name. So search all three. Each slug is the one that resolves. Don’t rebuild a URL from a headline: x.ai/news/biosafety-at-the-frontier serves “Biosecurity at the frontier,” and x.ai/news/grok-4-6-vertex-ai serves “Grok 4.6 on Gemini Enterprise Agent Platform.”
Live pages behind the figures, not listed below Rewritten in place
These pages carry no date and change without notice, so they can’t anchor a citation. Unless a dated article is named beside it, every price, context window, plan tier and security statement above comes from one of them, read October 15, 2026. Confirm directly before you rely on a figure, and keep your own dated copy.
docs.x.ai/developers/pricing: API, voice and Imagine prices, Grok 4.7 Fast pricing, the Deprecated label ongrok-voice-2.0, the 1.1x regional and 2x Priority rates, the Batch discount listdocs.x.ai/developers/models,docs.x.ai/developers/grok-4-7and the per-model pages: the May 2026 cutoff, reasoning effort settings, the empty Pricing sections, regionsdocs.x.ai/developers/release-notes: Grok 4.5 on the API July 8, EU console access July 17, the August 28 Imagine changes, the October 2 end of life forgrok-voice-transcribe-1.0, the October 14 voice changesdocs.x.ai/developers/faq/securityanddocs.x.ai/developers/advanced-api-usage/regions: SOC 2 Type 2, the GDPR heading, the HIPAA BAA route, 30-day storage, zero data retention, the US endpoint carve-outsdocs.x.ai/grok-bot/teams-and-enterprisesanddocs.x.ai/grok-bot/faq: the Individuals, Teams and Enterprise split, and the older SuperGrok plan namesx.ai/pricing: The X Subscription tiers, no certification namedx.ai/changelog/botandx.ai/changelog/build: Bot payments, Bot computer termination after 30 days, and Build memory changes. Changelogs, so read them yourselfx.ai/api,x.ai/voice,x.ai/safetyandstatus.x.aix.ai/enterprise: the $59 figure, an observation and never a price
Two migration guides are listed anyway Folder link fails
They sit in documentation. But they’re the only authoritative record of when an xAI model dies, and each carries its own last-updated date. As of October 15, 2026 both still show September 2, 2026. Watch the shape of the trap around them. The paths docs.x.ai/developers/migration and docs.x.ai/developers/deprecations failed to load on October 15, 2026, while the child pages resolve.
Six model cards on two hosts Not a dead host
Grok 4.7, Grok 4.6 and Grok 4.5 are on media.x.ai. Grok 4 Fast, Grok Code Fast 1 and Grok 4 are on data.x.ai. That host’s two index paths, data.x.ai/ and data.x.ai/model-cards, failed to load on October 15, 2026, while the files resolve. The host isn’t dead.
· Live at their URLs on October 15, 2026: the Grok 4.7 and Grok 4.6 cards and all three data.x.ai files
Two routes rest on Microsoft, not xAI No xAI source
Grok in Word, Excel and PowerPoint through the Microsoft Frontier Program, available since September 18, 2026. The admin setting that’s off by default. The exclusion of EU, EFTA, UK, government cloud and sovereign cloud customers. The Product Terms, DPA and Customer Copyright Commitment. All of it rests on Microsoft’s Learn page. Grok in Copilot Studio, with Microsoft’s safety warning, rests on Microsoft’s February 19, 2026 post and its Studio model page. None of it appears on x.ai/safety, x.ai/news, x.ai/pricing or x.ai/grok/business, or in a search of x.ai and docs.x.ai. Don’t mix it up with the xAI Frontier AI Framework, a safety policy dated June 30, 2026. Same word, different company.
· Microsoft’s Copilot Blog post “Expanding model choice in Copilot with Grok” carries page metadata modified September 14, 2026. The availability date and the terms come from Learn
A retitled article keeps its old URL Slugs aren’t IDs
The July 29, 2026 voice article now reads “Introducing Grok Voice 2.0” and names grok-voice-2.0, while its URL still says think-fast-2. The September 28 Team Bots article changed its headline the same quiet way. Never rebuild a model ID from a slug. Take the ID from the docs page that bills it.
grok-voice-3.0 at $0.08 per minute; grok-voice-latest now points to it; same API as 2.0↗Introducing The X SubscriptionxAI · October 12, 2026 · Plus, Premium, Super, Ultra, Teams and Enterprise covering Grok, Grok Bot, Cursor and X Premium; existing subscribers unchanged↗Team Bots: shared AI teammates that learn as they workxAI · September 28, 2026 · shared Bots in public beta on Teams and Enterprise plans; no price published↗How SpaceXSI is using Grok Bot to scale customer supportxAI · September 22, 2026 · xAI’s own support desk figures on its own data: vendor self-reporting, not evidence↗Introducing Grok 4.7xAI · September 21, 2026 · the current flagship: 500k context, $2.00 / $0.50 / $6.00 below 200,000 tokens, reasoning effort low to xhigh, and a fast variant with no published ID↗Introducing Grok Voice Transcribe 2.0xAI · September 18, 2026 · $0.10 per hour batch and $0.20 streaming; announced 1.0 deprecation “in the coming weeks” and still offers a 1.0 pin, though 1.0 reached end of life on October 2, 2026↗Memory in Grok BuildxAI · September 16, 2026 · persistent project memory written to markdown across sessions↗Setting Grok Bot loose on procurementxAI · September 4, 2026 · xAI’s own internal case study on its own spend data: vendor self-reporting, not evidence↗Grok Bot for EnterprisexAI · September 3, 2026 · access, network and audit controls; the free-usage offer expired September 17, 2026↗Designing Grok Bot for a world of persistent agentsxAI · September 3, 2026 · the five Grok Bot primitives and the introduction of Routines↗Biosecurity at the frontierxAI · September 1, 2026 · LatchBio third-party safeguards evaluation of Grok 4.6↗Grok Bot now works with XxAI · August 29, 2026 · first version of the X integration↗Grok Bot is now included with more plansxAI · August 26, 2026 · expansion from three plans to eight↗Grok 4.6 on Microsoft FoundryxAI · August 26, 2026 · Grok 4.6 in Microsoft’s model catalog↗Grok 4.6 on Gemini Enterprise Agent PlatformxAI · August 21, 2026 · Grok 4.6 in Google’s model catalog↗Grok 4.6 on Amazon BedrockxAI · August 19, 2026 · a dated article at its own URL, not a release note↗Grok Build on web and mobilexAI · August 19, 2026 · also a dated article, not a release note↗Grok 4.6 in GitHub CopilotxAI · August 14, 2026 · the first Microsoft surface for Grok 4.6, five days before Bedrock↗Cursor is now a part of SpaceXCursor · August 14, 2026 · acquired by SpaceX, completing a process begun in April · no terms disclosed↗Introducing Grok 4.6xAI · August 12, 2026 · the flagship announcement, including the fast variant said to cost twice the price↗Imagine Image 2.0xAI · August 7, 2026 · the dated article behind the image version change↗Imagine Video 1.5 with ReferencesxAI · July 31, 2026 · reference-guided video generation↗Introducing Grok Voice 2.0xAI · July 29, 2026 · grok-voice-2.0 at $0.08 per minute of audio, and the August 5 grok-voice-latest move; retitled without an edit note, slug unchanged↗Introducing Build ModexAI · July 28, 2026 · a dated Build release published outside the release notes↗Grok 4.5 in GitHub CopilotxAI · July 28, 2026 · the prior generation in Copilot, just over two weeks before 4.6↗Introducing Grok in Google WorkspacexAI · July 24, 2026 · free add-on for Sheets, Slides and Docs↗Workflows in Grok BuildxAI · July 23, 2026 · packaged repeatable work inside Build↗Grok 4.5 EverywherexAI · July 22, 2026 · rollout to iOS, Android, web and X↗Introducing Grok for OutlookxAI · July 21, 2026 · summarization, drafting and triage↗Introducing Grok for ExcelxAI · July 20, 2026 · free Microsoft 365 add-in↗Introducing Grok 4.5xAI · post byline July 16, 2026 · the prior generation: model, pricing and Cursor training↗Automations in GrokxAI · July 16, 2026 · scheduled and email-triggered runs↗Grok Build is now open sourcexAI · July 15, 2026 · agent loop, tools, TUI and extension systems↗21 New Flagship Grok VoicesxAI · July 6, 2026 · the voice library behind the speech products↗Introducing the Voice Agent BuilderxAI · July 1, 2026 · still marked Beta, not GA↗Introducing /goalxAI · June 22, 2026 · long-running task delegation↗Grok on DatabricksxAI · June 18, 2026 · the fifth third-party catalog, and it predates the August wave↗Grok for WordxAI · June 18, 2026 · the second add-in, a month before the July releases↗Grok on Amazon BedrockxAI · June 17, 2026 · the original Bedrock listing; only Grok 4.6 on Bedrock was new in August↗Grok Imagine Video 1.5xAI · June 16, 2026↗Grok for PowerPointxAI · June 16, 2026 · the first add-in in the program↗Introducing Grok BuildxAI · May 25, 2026 · the coding CLI agent↗Skills in web, iOS, and AndroidxAI · May 18, 2026 · the dated release behind reusable skills on the consumer surfaces↗New Compute Partnership with AnthropicxAI · May 6, 2026 · an article the news index has omitted at times while the URL resolved↗Grok Build 0.1 on APIxAI · Build on the API surface · the model ID is grok-build-0.1↗xAI joins SpaceXxAI · February 2, 2026 · SpaceX’s acquisition of xAI↗Introducing Grok Business and Grok EnterprisexAI · December 30, 2025 · the dated launch of the Business and Enterprise tiers↗Migration guide: grok-imagine-image-quality retires November 2, 2026xAI developer documentation · last updated September 2, 2026 · checked October 15, 2026 · a reference page and the only authoritative record of this retirement and of the $0.01 per image price delta↗Expanding model choice in Copilot with GrokMicrosoft Copilot Blog · page metadata modified September 14, 2026 · Microsoft’s announcement of Grok models in Copilot; no xAI page carries it↗More choice, more flexibility: xAI Grok 4.1 Fast now available in Microsoft Copilot StudioMicrosoft Copilot Blog · February 19, 2026 · Grok in Copilot Studio: preview, US makers only, off by default, under xAI’s own Enterprise terms and DPA↗SpaceXAI as a subprocessor in Microsoft Online ServicesMicrosoft Learn · page date September 18, 2026 · checked October 15, 2026 · a live page and the only authoritative record of the Frontier route’s availability date, admin setting, exclusions and terms↗Select a primary AI model for your agentMicrosoft Learn · last updated October 14, 2026 · checked October 15, 2026 · a live page and the only authoritative record of Microsoft’s Grok safety warning and the Grok 4.2 listing in Copilot Studio↗Cursor PricingCursor · undated live page · checked October 15, 2026 · names X Subscription Corp as the only seller of new subscriptions↗Cursor help: Pricing and plansCursor · undated live page · checked October 15, 2026 · switching an existing plan to The X Subscription is optional and permanent↗SpaceXSI for BusinessxAI · undated live page · checked October 15, 2026 · the only authoritative record of the $30 per user Business price and the Business compliance badges↗Speech to speech, xAI developer docsxAI developer documentation · undated live page · checked October 15, 2026 · no dated article records the grok-voice-2.0 deprecation; this page states it, the pin instruction and the alias target↗Migration guide: the May 15, 2026 model retirementsxAI developer documentation · last updated September 2, 2026 · checked October 15, 2026 · a reference page and the only authoritative record of the eight models switched off on May 15, 2026 and their replacements↗Vendor claims, named as such Attributed inline
None of these is an independent finding. Each is attributed wherever it appears.
- Elon Musk’s “Opus-class” description of Grok 4.5: vendor positioning
- “Twice as fast, at half the price of comparable models” for Grok 4.7, and its benchmarks: vendor claims on vendor-chosen tests
- 59.2% refusal and 64.8% completion for Grok 4.6: produced by LatchBio, published by xAI
- September 4 procurement and September 22 support figures: xAI measuring its own agent on its own data
- Isolation, governance, privacy and adoption statements for Grok Bot and Team Bots: vendor claims
- Grok Voice 3.0 as “the world’s most intelligent speech-to-speech model,” its 86.9 index score and the Starlink call-center figures: vendor claims and self-report
- More usage per dollar on each X Subscription tier than the plan it replaces: vendor claim
Arithmetic, not published figures Calculated
These are calculations on xAI’s own rates and dates. The 60 percent voice rise is $0.05 to $0.08 per minute of audio. The $0.004 text-input charge is the same on both models, so the figure describes the audio rate, not total cost of ownership. The 14 to 20 percent Imagine cut comes from the published per-image rates and the stated $0.01 delta: $0.01 off $0.07 is 14 percent, off $0.05 it’s 20. The $0.42 for six seconds of 720p video is six times the $0.07 per-second rate. The 18 days to November 2 and the 65 days since the Grok Bot launch count from October 15, 2026. The 2x and 1.5x Grok 4.7 Fast multipliers are xAI’s own.
Sixteen open questions Unconfirmed
Each is marked unconfirmed rather than stated, for the reason given.
- When
grok-voice-2.0stops answering: deprecated October 14, 2026, no end date - Whether
grok-voice-think-fast-1.0still answers, and at what rate: its model page renders with an empty Pricing section, no price-table row, and the July 29 article now calls it Grok Voice 1.0 - Whether the older Think Fast 2.0 string and
grok-voice-2.0are one ID: the article names onlygrok-voice-2.0and no page describes a rename - Whether Grok 4.6 is deprecated, retired or demoted: no retirement date anywhere, and its developer guide URL now serves Grok 4.7
- The ID of Grok 4.7 Fast: priced on the docs, no ID on any page; the Grok 4.6 fast variant has neither
- The publish date and full text of Microsoft’s Copilot Blog post: its page date reads September 14, 2026, and Learn dates availability to September 18, 2026
- Whether any xAI page mentions the Frontier route: none of
x.ai/safety,x.ai/news,x.ai/pricingorx.ai/grok/businessdoes - The regions on
status.x.ai: it publishes no region list in text - What SuperGrok Lite cost, and whether SuperGrok, Plus, Lite and Heavy can still be bought new: gone from the pricing page, still named in the Grok Bot FAQ
- Whether Teams on
x.ai/pricingand Business onx.ai/grok/businessare one tier: neither page mentions the other - Whether HIPAA is offered on Business: a badge with no plan or BAA detail
- When existing SuperGrok, Cursor and X Premium subscribers can switch: rolling out, no date
- X Premium+ entitlements for Grok Build and Grok for Outlook: no xAI page ties either to standalone X Premium+
- Whether Grok Bot has left beta: no GA statement 65 days after launch, and Team Bots still says public beta
- When the release notes gained “2.0 as the default” and the docs gained Grok 4.7 Fast pricing: rolling pages with no history
- Why
x.ai/enterpriseserves a $59 boilerplate page: no xAI page explains it
AI Mindset