andregoncalves/dsh-balance ↗★ 0
@andrecgoncalves/dsh-balance
Provider-aware account balance chip for the DeepSeek Harness web sidebar: DeepSeek, OpenRouter, Moonshot/Kimi, Zhipu/GLM, and MiniMax.
AI 분석
核心用途是在 DSH 界面中直观监控多 API 服务商的账户余额。适合使用多种大模型、需要频繁关注 Token 消耗和充值状态的开发者或高频用户，支持从凭据配置文件中自动读取 API 密钥。
설치
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:andregoncalves/dsh-balanceConfiguration
DeepSeek resolves DEEPSEEK_API_KEY through the Harness credentials seam (for example ~/.dsh/.credentials.yaml). The other providers try the seam first, then fall back to the ambient launch environment (process, the invoking project's .env, then the Harness home's .env).
| Provider | Credential names tried, in order |
|---|---|
| DeepSeek | DEEPSEEK_API_KEY |
| OpenRouter | OPENROUTER_API_KEY |
| Moonshot / Kimi | MOONSHOT_API_KEY |
| Zhipu / GLM | ZAI_API_KEY, GLM_API_KEY, ZHIPU_API_KEY |
| MiniMax | MINIMAX_API_KEY, MINIMAX_CN_API_KEY, MINIMAX_API_TOKEN |
To share one credential plane with the model adapter, store the key in ~/.dsh/.credentials.yaml and add apiKeyEnv to the route. Zhipu's account endpoints expect the key verbatim (no Bearer prefix); the host applies the right scheme automatically. Moonshot and Zhipu mirror across two regional hosts, so a key valid on only one site falls through to the other before the request is reported as failed.