Mureka Billing

Mureka Billing is the pack's reality check: it queries the Mureka API for your account usage and remaining credit and shows the answer on screen. It doesn't generate anything, takes no audio, and returns no output wires. It's a dashboard node for the one number that actually matters with a paid API - how much you have left before the "out of credits" errors start.

Inputs

• api_key (MUREKA_API_KEY) - the same key node the generation nodes use.
• A wildcard * input. This is the README's trick: the * input accepts any connection purely so you can link this node anywhere in your graph without affecting data flow. Stick one before your generation step to confirm you have budget, and one after to see what a run cost you.

How it works

When the graph runs, the node calls Mureka's billing endpoint with your key and displays the usage and credit figures in its widget. It's an output node - it's the end of its branch, so there's nothing to wire onward. To make it run, just connect something into that * input so it's part of the executing graph, then queue the workflow and read the result.

Why you should use it

Because generation costs are real money and they vary by model. The README's cost-management advice basically boils down to: mock-test with Mureka Mock Generation while you build, and watch your balance with Billing before you run real batches. It's especially worth wiring in while you're experimenting with the model dropdown on Song or Instrumental - different models burn credits at different rates, and the billing node tells you what you actually spent.

Installing

Standard for the pack: ComfyUI Manager → Install Custom Nodes → search "Mureka API", or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/leewinder/comfyui-mureka-api.git

No models, no heavy dependencies - it's a thin API wrapper.

Troubleshooting

• Billing node shows nothing or errors: check the key. Same key, same 401 rules as the generation nodes.
• It doesn't run when you hit Queue: an output node only executes if it's connected into the running graph - that's the whole point of the * input. Give it a wire.
• Numbers look off: it reflects Mureka's own account view, so if you're comparing it to a different dashboard you're looking at two sources. Trust the API's figures for billing.

It's not glamorous, but it's the node that stops you from discovering an empty account at the worst possible moment.