Sibling of the Kimi provider. Moonshot issues separate accounts and API keys for api.moonshot.cn (China) vs api.moonshot.ai (international) – these cannot share one key, so this is a distinct UsageProvider case (kimiCN) rather than a base-URL override.
Reuses KimiUsageFetcher.fetchBalance(apiKey:baseURL:) with baseURL hardcoded to https://api.moonshot.cn. Same response shape as the international provider.
Credentials
Token resolution order:
- Keychain token (stored from Preferences -> Providers -> Kimi (China)).
- Environment variable
KIMI_CN_API_KEY. - Environment variable
MOONSHOT_CN_API_KEY.
Keychain location
- Service:
com.sriinnu.athena.Runic.provider-credentials.v2 - Account:
kimi-cn-api-token
Key files
Sources/RunicCore/Providers/Kimi/KimiCNProviderDescriptor.swiftSources/Runic/Providers/Kimi/KimiCNProviderImplementation.swiftSources/Runic/Core/Stores/KimiCNTokenStore.swift
Read the source ↗ Checked against Runic 2.13.5 · 9730f91