AsaleSelling Kimi (Moonshot)
Two ways to connect Moonshot — a Kimi Code subscription by device code, or a platform API key billed against a balance. They behave differently.
Moonshot is one of two providers with two distinct connect paths, and they are not interchangeable.
Kimi Code subscription — device code
Sell → Connect a subscription → Confirm a code in the browser. You get a short code and a URL; approve it and the account connects.
The browser does not have to be on this machine. That makes Kimi one of the two providers connectable from a remote or headless session, where a loopback OAuth flow cannot work.
Kimi issues no OIDC identity token, so the account carries no vendor-side name. It is listed by provider and a local identifier rather than by email.
Moonshot API key
Sell → Connect with an API key. Paste a key issued in Moonshot's console.
This is not a subscription. It is metered against your balance, so every token you sell spends real money — the daily cap is the only thing standing between the market and your credit.
Capacity
Kimi publishes no token allowance at all — its limits are expressed as requests over a window, and the platform API is metered rather than capped. There is nothing to estimate, so the client declares a deliberately conservative 500,000-token window.
For Kimi, the window figure is a placeholder. Set a daily limit you are comfortable with; nothing else bounds this account.
Models it serves
kimi-k2.7-code, kimi-k2-thinking, kimi-k3.