Kimi Code Setup

onWatch tracks Kimi Code (the coding agent OAuth product) quotas via:

GET https://api.kimi.com/coding/v1/usages
Authorization: Bearer <access_token>

This is not the Moonshot Open Platform pay-as-you-go balance API (api.moonshot.ai / api.moonshot.cn).

Prerequisites

1. Install and log in with kimi-code only: docs — kimi login
2. Credentials file is searched only under the kimi-code store (in order):
   • $KIMI_CODE_CREDENTIALS or $KIMI_CREDENTIALS (explicit file; Docker/CI)
   • $KIMI_CODE_HOME/credentials/kimi-code.json
   • ~/.kimi-code/credentials/kimi-code.json

Legacy kimi-cli (~/.kimi, $KIMI_SHARE_DIR, $KIMI_HOME) is not supported.
A single dashboard tab must not touch two OAuth token chains (refresh rotation would invalidate the other store).

Token refresh policy

• If the kimi-code access token is still valid (expires_at with a 60s skew), onWatch never refreshes — it reuses the token the CLI already wrote.
• Refresh runs only when access is expired. Then onWatch may call:

POST https://auth.kimi.com/api/oauth/token
grant_type=refresh_token&refresh_token=...&client_id=17e5f671-d194-4dfb-9706-5516cb48c098

and rewrite the same kimi-code credentials file (mode 0600).

• On HTTP 401 with a still-unexpired access token, onWatch re-reads disk once (CLI may have rotated tokens) but does not force-refresh.

Enable

Auto-detect is on by default when credentials exist:

# optional explicit enable
KIMI_CODE_ENABLED=true

# optional disable
KIMI_CODE_ENABLED=false

Docker / CI without local files:

KIMI_TOKEN=<access_token>
# or
KIMI_CODE_TOKEN=<access_token>

For long-running daemons, prefer mounting the kimi-code credentials file:

KIMI_CODE_CREDENTIALS=/path/to/kimi-code.json

What is tracked

Dashboard quota cards (same rate-limit surface as Code CLI):

Card	Source	Meaning
7-day	usage	7-day utilization (used/limit). Product UI may show one decimal place; the API usually returns integer percents.
5-hour	limits[] with duration=300 + TIME_UNIT_MINUTE	Rolling 5-hour window

Insights also shows Membership plan name from user.membership.level:

API level	Display name
LEVEL_FREE	Free
LEVEL_BASIC	Adagio
LEVEL_STANDARD	Moderato
LEVEL_INTERMEDIATE	Allegretto
LEVEL_ADVANCED	Allegro
LEVEL_PREMIUM	Vivace

Other /usages fields (totalQuota, non-5h windows) are ignored. The membership site “total usage” bar (e.g. on My Quota) comes from a separate web API (GetSubscriptionStats) and is not tracked.

Timezones

resetTime values are UTC. The dashboard formats them in your configured timezone (Settings). Example: 2026-07-14T16:13:41Z → 2026-07-15 00:13 in Asia/Shanghai.

Verify

# after kimi-code login
kimi  # then check usage in the CLI if available

# or curl with the access_token from ~/.kimi-code/credentials/kimi-code.json
curl -sS -H "Authorization: Bearer $TOKEN" https://api.kimi.com/coding/v1/usages | jq .

Restart onWatch and open the Kimi Code dashboard tab.