AI Agent Hub
Back to plugins
🖥️

dsh-account-balance

Client Updated 2026.09.05

Run the following command in DeepSeek Harness:

dsh plugin install 305037991x-pixel/dsh-account-balance

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install 305037991x-pixel/dsh-account-balance in the DeepSeek Harness terminal to install it; the source is available at https://github.com/305037991x-pixel/dsh-account-balance.

About this plugin

Juggling accounts across both DeepSeek and OpenRouter means hopping between two dashboards every time you want to check how much credit you have left. dsh-account-balance pins a single chip into the conversation header of DeepSeek Harness Web: a ¥ figure on the left for DeepSeek and a $ figure on the right for OpenRouter's available balance (credits minus usage), so you can glance and move on without switching tabs.

Hover the chip and two mini-panels slide out. The DeepSeek side lists total balance, top-ups and gifted credits; the OpenRouter side shows available, total credits and total usage. Each source is fetched independently, so if one API call fails only that side shows an error badge while the other keeps working. The chip auto-refreshes every three minutes and offers a manual button to refresh both at once; navigating between sessions reuses a module-level shared cache so no duplicate requests are made. All API keys are resolved on the host side — the browser never sees a plaintext credential.

If you routinely call both platforms from DeepSeek Harness and want balances visible at a glance, securely and with zero extra browser load, this little chip is built for you.

Use Cases

  • Using both DeepSeek and OpenRouter APIs and needing to track available balances at a glance
  • Avoiding repetitive tab-switching to check credit status in separate dashboards
  • Keeping API keys secure on the host side while balance data renders in the browser

Best For

  • Developers calling both DeepSeek and OpenRouter APIs from DeepSeek Harness daily
  • Team members who are balance-sensitive and want to minimize manual credit checks
  • Users who prioritize key security and do not want plaintext credentials in the browser