AsaleSelling Grok (xAI)
Connect a Grok CLI subscription by device code, or an xAI platform key — and why some Grok model ids are deliberately not advertised.
xAI connects the same two ways as Moonshot, with one extra wrinkle in its model ids.
Grok CLI subscription — device code
Sell → Connect a subscription → Confirm a code in the browser. Approve the short code and the account connects. As with Kimi, the browser need not be on this machine, so this works from a remote session.
xAI API key
Sell → Connect with an API key, using a key from xAI's console. Metered against a balance, not a plan — selling from it spends money, and your daily cap is what bounds that.
Capacity
Like Kimi, Grok publishes no token allowance. The client declares a conservative 500,000-token window and leans on your daily cap instead.
Models it serves
grok-4.5, grok-4.3, grok-build-0.1.
The catalog spells models the way OpenRouter does, and for xAI that is sometimes not the way xAI's own API spells them — the catalog may list grok-4.20 while the vendor serves only grok-4.20-0309-reasoning and -non-reasoning.
Advertising the catalog spelling would fail after a request had been matched, preauthorised and routed to you, and you would wear a failure that was never yours. So those rows are simply not advertised.