Sibling of the z.ai / GLM provider. Zhipu AI issues separate accounts and API keys for open.bigmodel.cn (China) vs the international z.ai brand – this is a distinct UsageProvider case (zaiCN).
Reuses ZaiUsageFetcher.fetchUsage(apiKey:baseURL:) with baseURL set to https://open.bigmodel.cn/api/monitor/usage. Unverified: this mirrors z.ai’s /quota/limit, /model-usage, /tool-usage path shape onto the bigmodel.cn host, but has not been confirmed against a real bigmodel.cn account – if the endpoint path differs, the fetch will surface an explicit error rather than showing wrong numbers.
Credentials
Token resolution order:
- Keychain token (stored from Preferences -> Providers -> z.ai (China)).
- Environment variable
BIGMODEL_API_KEY. - Environment variable
ZHIPU_API_KEY.
Keychain location
- Service:
com.sriinnu.athena.Runic.provider-credentials.v2 - Account:
zai-cn-api-token
Key files
Sources/RunicCore/Providers/Zai/ZaiCNProviderDescriptor.swiftSources/Runic/Providers/Zai/ZaiCNProviderImplementation.swiftSources/Runic/Core/Stores/ZaiCNTokenStore.swift
Read the source ↗ Checked against Runic 2.13.5 · 9730f91