On October 7 at 06:46 UTC, Elon Musk posted: “Going forward, SpaceX will use the best back end model for any given task, including Claude Opus 5.5, MidJourney, Suno and other leading APIs.” He added: “Whatever is most likely to give you the best outcome.” Competitor CellCog, which builds AI employees in the same category and discloses the conflict, reported the post passed 30 million views in seven hours.
What the post does not carry matters as much: no start date, no task-to-vendor map, no pricing. Seventeen days later the routing still has no Grok Bot changelog entry — the log’s latest release is v0.66.0, dated October 2 — and xAI’s own Grok Bot page does not mention Claude or routing at all. Read that page today and what you find is entitlement: Grok Bot included with Premium at $30 a month, Super at $100, Ultra at $200, Teams and Enterprise, and “generally available for Enterprise, as well as for teams on the Teams plan.” Third-party plan tables also list SuperGrok Heavy and the paid Cursor tiers; after the October 12 X Subscription change, legacy SuperGrok Heavy at $300 was pulled from new sales while existing subscribers keep it, and when a SuperGrok grant and a Cursor grant both attach to one account, the larger grant applies rather than the two stacking. The access ships. The routing is announced, not documented.
The mechanics live in the documentation, as read by CellCog on October 7. Grok Bot has “no customer-facing model picker”; the serving mix “can change over time with no fixed vendor set guaranteed”; and “billing follows the serving model.” The only place a user sees which model actually answered is the usage analytics, which show the serving model for each request including failovers. The named back-ends are Claude Opus 5.5 for reasoning and coding work, Midjourney for images and Suno for music — that task-to-model mapping is reported inference, not something the post specified. Grok 4.7, released September 21 and trained on the Grok Bot harness itself, went unmentioned.
Who pays depends on where a task lands. List prices, compiled by CellCog from published rate cards, put Claude Opus 5.5 at $4 input and $20 output per million tokens against Grok 4.7 at $2 and $6 for prompts under 200,000 tokens. Grok Bot’s own page says subscriptions include weekly usage with “additional usage billed based on token cost” — but the on-demand rate for a Claude-served request is unpublished, and xAI has not said whether weekly allowances shift when the serving model does. The bill is metered against a mix the platform is free to change.
The instinctive read is that xAI conceded model superiority. The structural read is that it stopped competing where its rivals are strongest and moved the contest up one floor. Whoever owns the routing logic, the data path and the meter owns the customer relationship regardless of which model bills the tokens — the same leverage Forkast traced in four money models earlier this month. The plumbing already existed: Grok Bot runs on Cursor accounts and Cursor-hosted computers, the documentation says Cursor manages model selection, and a May 2026 agreement gave Anthropic access to the Colossus 1 supercomputer. A gateway is cheap to build when the switchboard and the supplier relationship both predate the announcement.
For buyers, the moat is a governance gap. The documentation puts the model allowlist behind Enterprise and then says “enforcement is not guaranteed,” with the security FAQ asking administrators to acknowledge that Grok Bot may not follow the list. A task served by Claude sends context to Anthropic, and buyers whose contracts limit subprocessors are told to contact their account team before rolling Grok Bot out. The enterprise can state a preference; the platform retains the override. That is the trade — outcome quality chosen per task, in exchange for a selection process no customer controls.
Two indicators separate a durable moat from a press-cycle integration. A changelog entry carrying model-specific billing would make the routing a productized feature with a real start date; an admin-enforced routing policy would show the black box becoming a control panel. Until one lands, the honest description is that the interface is the asset, the models are interchangeable supply, and the switchboard’s settings remain unpublished.
