{
 "schema_version": 1,
 "generated": "2026-10-24",
 "id": "aisland-sjl-dsh-usage--track-multi-provider-balances",
 "repo": "Aisland-SJL/dsh-usage",
 "repo_url": "https://github.com/Aisland-SJL/dsh-usage",
 "repo_slug": "aisland-sjl-dsh-usage",
 "title": "Track balances for OpenRouter, Z.ai, and Kimi together",
 "page_title": "How to track balances for OpenRouter, Z.ai, and Kimi together with DSH Usage",
 "summary": "Configure extra provider keys so the panel shows balances across several AI providers.",
 "who": "A person who pays for more than one model provider and wants all remaining credit in one place.",
 "problem": "Each provider has its own billing page, so remaining balance is easy to forget until a request fails.",
 "outcome": "The Balance widget shows each configured provider's balance, and unsupported providers show an explicit no-public-balance state.",
 "steps": [
  "Add OPENROUTER_MANAGEMENT_KEY (a Management Key, not an inference key) and ZAI_API_KEY to Harness credentials.",
  "Confirm Moonshot / Kimi profiles under llm-pi-ai exist, since they are discovered automatically and reuse their apiKeyEnv.",
  "Install with `dsh plugin --profile web add \"github:Aisland-SJL/dsh-usage\"` and restart `dsh web`.",
  "Use the provider picker in the Balance widget to switch between providers.",
  "Press refresh to force an upstream query for the selected provider."
 ],
 "agent_prompt": "In the repo Aisland-SJL/dsh-usage, list the providers from the providers endpoint on <dsh web URL> and report each balance status. Verify that any provider without a key is reported as not configured rather than showing a guessed value.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The README says real account queries are separate acceptance work and that offline tests do not establish acceptance for every account.",
 "category": "Data and analytics",
 "tags": [
  "Data and analytics"
 ],
 "lang": "javascript",
 "requirements": [
  "DeepSeek Harness host, version 0.2.0-rc.2 for v0.3.1 of this plugin, with the dsh CLI installed",
  "An API key for each provider you want to query, configured through Harness credentials (for example DEEPSEEK_API_KEY)",
  "Node.js and npm only if you plan to run the offline tests or develop the plugin"
 ],
 "risk": "sensitive",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [
  {
   "tag": "credentials",
   "notice": "Several provider keys are involved, and the OpenRouter key must be a Management Key, so check each key's scope before storing it in Harness."
  }
 ],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/aisland-sjl-dsh-usage/track-multi-provider-balances/",
 "md": "https://dedupedai.com/use-cases/aisland-sjl-dsh-usage/track-multi-provider-balances/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/aisland-sjl-dsh-usage--track-multi-provider-balances.json",
 "api_version": "v1"
}