zhenzhen-seedance2-low-price-api-settings

Every "lowprice" node in the zhenzhen pack - the Qwen image and TTS nodes, both Seedance 2.0/2.5 nodes, the Suno node, the layer-decomposition node - has an api_config input instead of its own key field. Comfly_seedance2_low_price_settings is the node that produces that api_config. It's the plumbing node, not the glamorous one: it exists so you configure your token once and feed the same credentials to every domestic-shop node in the workflow. Think of it as the pack's shared keychain.

It's also genuinely tiny. Two inputs, one output:

• base_url - defaults to https://api.seedance.nz, the domestic low-price shop (roughly 75% of the overseas rate per the README). You can point it at the overseas https://ai.t8star.org instead if you'd rather bill against that shop.
• api_key - your token from whichever shop you're using. Everything downstream inherits it.

The single output, api_config, is a dictionary that carries both values forward - wire it into any low-price node's api_config input. The node is OUTPUT_NODE-adjacent plumbing with no heavy computation; it just normalizes the base URL and trims your key so the rest of the pack doesn't have to re-validate it.

One implementation detail worth knowing: the low-price transport uses a bundled TLS root certificate, loaded via a custom SSL adapter when it talks to the default shop. If you ever see a TLS-related error that won't go away after an update, the README's "delete the node and re-add it" advice sometimes hides a stale copy of that bundled cert - re-cloning the pack fixes it.

Installing it

It ships in the pack, so the install is the pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-zhenzhen

or ComfyUI Manager, search "Comfyui-zhenzhen", restart. No models, no extra dependencies beyond the pack's normal HTTP stack.

Common issues

• Every low-price node says "no API key" - the settings node isn't connected. Every downstream node needs its api_config input wired to this node's output.
• Typed the key, still failing - check for a stray space; the node trims it, but only if you didn't wire an already-broken config forward.
• TLS errors after an update - re-clone the pack to refresh the bundled certificate rather than hunting your firewall.

It's not exciting, but it's load-bearing: on the domestic shop, you'll typically build one of these at the top of every workflow that touches the low-price nodes.