Labnana Subscription Info

Labnana runs on prepaid credits, and ComfyUI-Labnana is honest about the business model: every generation you run costs a few credits, and running out mid-job is error code 26004 - "insufficient credits." LabnanaSubscription is the node that tells you how many credits you actually have before you find out the hard way. It's a read-only account query: wire in the client, run it, and read your balances off the outputs. It never spends anything.

How it works

It calls the user subscription endpoint and parses the response into typed outputs. Because balances change server-side (every generation spends them, and monthly credits may reset on a cycle), the node deliberately skips ComfyUI's cache - it always re-queries on every run, so what you see is current.

The only input is client, straight from a Labnana API Client node. The outputs are the useful part:

• total_credits (INT) - the big number, what you have to spend right now.
• monthly_credits and permanent_credits (INT) - the split between credits that roll over/expire on a cycle and credits that are yours forever. That distinction matters more than people expect, which is exactly why the API exposes them separately.
• limited_time_credits (INT) - promo or campaign credits with an expiry attached.
• paid_status (BOOLEAN) - whether you're on a paid plan. False is your cue that free-tier behavior applies (like retryable busy responses at peak times).
• info_json (STRING) - the full raw subscription record, pretty-printed.
• free_usages_json (STRING) - your free-usage allowances, also as JSON.

That last one is worth a second look. Labnana lets 1K/2K generations consume a shared account-level free allowance before touching your credits - but free usage never covers 4K. So free_usages_json is where you find out whether the cheap generations are effectively free right now.

Install

Search Labnana in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/exoticknight/ComfyUI-Labnana.git

Restart. Only dependency is requests, and you need your ls_... key configured in the client node or via LABNANA_API_KEY.

Gotchas

• Read the JSON when the ints aren't enough. total_credits is the headline, but info_json carries the details - plan status, expiry dates, free allowances - that the typed outputs flatten away.
• Pair it with Labnana Estimate Credits for a real budget check. Balance minus next job's estimated price is the number that actually tells you whether you can afford that 4K batch you were about to run.
• It's a single account view. If you run multiple Labnana keys, you get whichever account the client node is configured with - swap the client, not the node.

For a single-account hobbyist this node is a nice-to-have you'll check a few times. For anyone running paid pipelines, put it at the top of the workflow as a cheap habit: knowing your balance before a batch is how you avoid discovering 26004 in the middle of it.