How do I check my Kimi (Moonshot AI) API balance?
Last updated: 26 September 2026 · Deutsch
Log in at platform.kimi.ai and open the fee-detail page in the console. Or call GET https://api.moonshot.ai/v1/users/me/balance with your API key. The field available_balance is what you can still spend.
Below: what the three balance fields mean, what happens at zero, why there is no usage endpoint, and why you must pick the right one of two platforms. Moonshot has renamed its platform before; this page reflects its own documents as of the date above.
Moonshot, Kimi and two platforms
Moonshot AI runs the Kimi API. Its developer site has moved:
platform.moonshot.ai now forwards to platform.kimi.ai, and
platform.moonshot.cn forwards to platform.kimi.com. The API
hosts keep the old names: api.moonshot.ai and
api.moonshot.cn.
These are two separate platforms, not two doors to one account. Kimi tells users
outside mainland China to use platform.kimi.ai. Accounts, balances and
keys on each side stand alone. A balance you top up on one platform does not show on
the other.
The Open Platform is also apart from Kimi’s other products. Kimi’s help pages say plainly that the Open Platform, Kimi Code and the Kimi membership do not share keys or balances. A membership does not turn into API balance, and API balance cannot buy a membership or a Kimi Code plan.
In the console
Log in at platform.kimi.ai and open the fee-detail (billing details) page
in the console. According to Kimi’s help pages it shows:
- your current balance,
- usage per day,
- usage and cost per model,
- past spend over time.
Billing figures lag behind, and Kimi names no fixed delay. So today’s spend on this page is an early figure, not the final one.
With the API
The balance endpoint is a plain GET with your API key as a bearer token:
GET https://api.moonshot.ai/v1/users/me/balance
Authorization: Bearer <your API key>
On the China platform, the path is the same and the host is
api.moonshot.cn. The reply holds three numbers:
available_balance— what you can still spend: cash and vouchers added up. This is the figure that decides whether your calls go through.voucher_balance— credit from vouchers. It cannot go below zero.cash_balance— the money you paid in. It can go below zero; a negative figure means you owe Moonshot money.
The currency depends on the platform. The international docs give all three fields in US dollars; the China docs give them in yuan. The reply itself carries no currency field, so your code has to know which platform the key comes from.
Vouchers from top-up campaigns also land in voucher_balance. Kimi’s help
pages point you to this endpoint to check whether one has arrived.
What happens at zero
Once available_balance is zero or below, Kimi rejects calls to its models with the error exceeded_current_quota_error. You then need to top up, or check whether your voucher is still valid.
The same error also comes when the account is overdue or a voucher has run out. Kimi lists it among the causes of a 429 reply, next to rate limits and overload. Topping up clears this one. For overload, Kimi says, adding money does not help.
Kimi offers two brakes before you reach zero:
- Balance alerts. Kimi advises turning them on; the platform then tells you when the balance falls below an amount you set.
- A daily budget per project, set in the project settings of the console. Once a project reaches it, Kimi rejects all API calls in that project. Because billing lags, the cap can take a while to take effect.
No endpoint for usage
The API reports the balance and nothing more. Daily usage, cost per model and past spend are only on the fee-detail page in the console.
If you want your own record, one way is to read the balance at fixed times and note how far it drops. That works as long as you do not top up in between, and it cannot tell models or projects apart. How the other AI APIs handle costs, and where Kimi stands among them, is in AI API costs at a glance.
When the key returns 401
Most likely the key belongs to the other platform. Keys from platform.kimi.ai work only with api.moonshot.ai, keys from platform.kimi.com only with api.moonshot.cn. Sent to the wrong host, a valid key returns 401.
Kimi’s own checklist adds two more causes: a key from Kimi Code instead of the Open Platform, and old settings in local tools that still point to another key or host. Check those before you make a new key.
In AI Cockpit
The Kimi K3 card sits in the Mac menu bar and in the app on iPhone and iPad. On Apple Watch (via the iPhone app) Kimi shows as a row with the available balance. You enter your API key in Settings and pick the platform, international or China; the card then calls the balance endpoint described above.
- The available balance, with the voucher and cash parts below it.
- A badge “active” or “empty”, and a warning in the card header once the available balance is zero or below.
- A note on the card that Kimi gives no usage through the API.
- On the Mac only: if you also enter an access token for the Kimi Code plan, the card shows that plan’s session quota, with the share used and its reset time. By default it turns to a warning colour at 75 and 90 per cent. You can also put it in the menu bar.
What it does not do: top up, show daily or monthly spend, or set alerts and budgets on Kimi’s side. The card always labels the amounts in US dollars. On the China platform Moonshot counts in yuan, so read the figure as yuan there.
How AI Cockpit reads the costs of the other APIs is in AI API costs at a glance. Short answers to other questions are on the FAQ page.