Asalebeta

Selling 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.

Like Moonshot, xAI has two ways in, plus one extra wrinkle around model names.

RouteWhat you are sellingRisk
Grok CLI subscription (device code)Subscription capacity you have already paid forLow — when it runs out, it runs out
xAI platform API keyThe actual money in your account balanceHigh — every token you sell spends your money

If you are not sure, take the subscription route.

Time needed: about 10 minutes | Platform fee: 8%

Selling requires your machine to reach the upstream vendor

When you sell, the machine that actually asks the vendor is your own computer, using your own account — so connecting the account, the automatic renewals afterwards, and every job you do for a buyer all require that path to work. In some regions a direct connection is refused (the client shows 403); this is not a sign-in problem, and signing in again will not help.

The client ships with Settings → Network → Upstream proxy (auto / force direct / manual, supporting http://, https:// and socks5://), and you can click Test connection to verify it. See Install the client.

Step 1: Install the Asale client and sign in

Not installed yet? Work through Install the client: download → install → register and sign in on the Account page.

The Asale client

xAI cannot pop open a browser sign-in either; it uses a device code.

Step 2: Start the device-code connection

Sell on the left → click Confirm a code in the browser.

The three buttons in the connect-a-subscription area

  1. Note the code on screen

    The client shows a URL and a code.

    The device-code screen: URL plus code

  2. Open that URL in any browser

    The browser does not have to be on this machine — a phone or another computer works. So even if Asale is on a headless server, you can still connect.

  3. Sign into xAI and enter the code

    Confirm, come back to the client, and it continues automatically; the account appears in the Subscription accounts list.

Route two: an xAI platform API key

This route spends your own real money

An xAI platform key bills against your balance; it is not a plan. Selling through it consumes the money in your account, while Asale settles your earnings at the market price — the difference can be positive or negative.

Your daily cap is the only boundary. On this route, setting a cap is mandatory.

  1. Issue an API key in the xAI console

    Sign into the xAI developer console, create a new API key, and copy it.

  2. Back in the client, click "Connect with an API key"

    Sell on the left → Connect with an API key.

    The API key connection dialog

  3. Paste the key and give it a label

    Paste the key, nothing else — no Bearer , no quotes, no spaces. The label is optional. Click Connect.

Step 3: Set the daily limit (especially important for Grok)

Sell on the left → click the pencil (Edit limit) next to Daily sell limit on the account card. The Limits page on the left is a read-only usage view; you cannot set a selling cap there.

The daily sell limit

Grok's window figure is a placeholder too

Like Kimi, xAI does not publish a quota. The client conservatively reports 500,000 tokens — a number that stops nothing.

The only thing actually constraining this account is the daily cap you set. On the API key route, work backwards from "the most I am willing to spend today".

Step 4: Turn on the sell switch

Turn on Sell this account on the account card.

Which Grok models you can sell

grok-4.5, grok-4.3, grok-build-0.1.

Why some Grok names on the market are missing here

Model names in the market catalogue follow OpenRouter's spelling, and that is sometimes not xAI's own spelling — the catalogue may say grok-4.20 while xAI only serves grok-4.20-0309-reasoning and grok-4.20-0309-non-reasoning.

If jobs were taken under the market's spelling, the work would be assigned to you and the money held first, only to fail at xAI at the end — a failure and a reputation hit for nothing.

So those names are simply not used to take jobs. This is protecting you, not an omission.

Step 5: Confirm you really are selling

Per-model: check whether these models are selling.

RecordsSell tab: time, model, token count and earnings, job by job.

Selling earnings on the Records page

On the API key route, reconcile every day

Asale only knows what you earned, not what you spent on xAI's side. Open the usage page in the xAI console regularly and compare the two.

Step 6: Withdraw

WalletWithdraw → pick Solana or TRON → enter an address and an amount.

The withdrawal page

Pick the wrong chain and the money is gone

On-chain transfers cannot be reversed. Check twice before you submit.

Common questions

Can I use both routes at once? Yes — they are two separate entries, each with its own switch and cap.

Can I sell from a server with no graphical interface? Yes. Grok and Kimi are the only two vendors that can be connected this way — confirming the device code on your phone is enough.

How do I revoke an API key completely? Click Remove on the card, then delete that key in the xAI console.

Why does my model say "not shared here"? That name is not currently in the tradable list (the model-name problem above). Nothing to do; wait for the catalogue to update.