RunningHub Account Status

A little dashboard node. RunningHub is a cloud ComfyUI service that runs on credits (they call them coins), and when you're driving it from a local graph with the Addoor RHAPI nodes, it's handy to know your balance without alt-tabbing to their website. That's this node's whole job: ask RunningHub how you're doing.

How it works

Feed it your api_key and it returns two numbers: remain_coins, how much balance you've got left, and current_task_counts, how many jobs you currently have running or queued on their servers. It's an output node, so it'll show those values right on the canvas when the graph runs.

Both outputs are plain INTs, which is the useful bit - you can wire them into logic. Cheap version: just eyeball the number. Fancier version: gate a batch on it, or feed remain_coins into a comparison so a big automated run doesn't start when you're nearly empty.

RunningHub, like most cloud generation services, charges per job out of a prepaid credit balance - heavier workflows and bigger models cost more coins per run. So remain_coins isn't a vanity metric; it's the thing that decides whether your next fifty dispatched jobs actually complete or die halfway through. current_task_counts is the companion number: it tells you how much you already have in flight, which matters because plans cap concurrency, and piling on past that cap just gets jobs rejected.

Why you'd bother

If you're doing one-off runs, you probably wouldn't - you'd glance at the website. Where it earns its place is automation. Say you've built a graph that loops through a folder of prompts and dispatches each to RunningHub. Kicking off fifty jobs only to have them fail halfway because you ran dry is annoying and wastes the coins you did spend. Checking the balance first, or watching current_task_counts so you don't pile jobs past whatever concurrency your plan allows, keeps that tidy.

Watch for

Same credential caveat as the rest of the RHAPI set: api_key sits in plaintext on the node, so scrub it before sharing the workflow. And remember the numbers are a snapshot from when the node executed - if you're monitoring a long batch, you have to re-run it to refresh. It's not a live meter.

Installing ComfyUI-Addoor

ComfyUI Manager: Install Custom Nodes → search "ComfyUI-Addoor" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Eagle-CN/ComfyUI-Addoor.git
cd ComfyUI-Addoor
pip install -r requirements.txt

Restart, and it shows up under 🌻 Addoor / RHAPI alongside the rest of the RunningHub client nodes. It's only useful if you actually have a RunningHub account and key - on its own it's an account-balance readout for a service you may not use.