Zhenzhen API Settings

Every node in the T8mars/Comfyui-zhenzhen pack - the Seedream and Seedance wrappers, the Sora and Veo video nodes, the Suno and Midjourney ones - has an api_config input, and this is the node that feeds it. It's the front door to the whole pack, which matters because the pack itself is just a very thin storefront over someone else's cloud APIs. The models (Seedream V5, Seedance 2.0/2.5, Sora 2, GPT Image, Veo 3.1, Kling, Hailuo, Suno…) have no open weights, so "running them in ComfyUI" always means calling an endpoint. This node is where you say which endpoint and with whose key.

The name is a lie (in a good way)

"Zhenzhen API Settings" does not call any API and holds no key on its own. It builds a small config dict - base_url plus api_key - and hands it to the generation nodes, which do the actual HTTP work. That's the whole job, and it's exactly why the node feels boring: it's plumbing. It's also why it's the most important node in the pack: get the channel and key wrong here and every generator downstream fails in confusing ways.

The three inputs that matter

• api_base - a dropdown with three channels. Default is seedance_low_price, which points at https://api.seedance.nz, the author's "平价AI小铺" (budget shop) domestic site and the one most nodes are built around. zhenzhen points at https://ai.t8star.org, the overseas "AI工坊" main site, which in recent builds auto-fails over to ai.t8star.cn if the primary is unreachable. ip lets you aim at your own endpoint.
• apikey - the token from whichever site you picked. Every generation node will reject an empty or wrong key with "Seedance API key is required…", so expect that error on the generator, not here.
• custom_ip - only used when api_base is ip (e.g. http://104.194.8.112:9088). Select ip without filling it and the node raises "you must provide a custom IP address". The optional skip_error toggle just controls whether a failure throws or returns a default empty result.

The node outputs apikey (a pass-through string) and the api_config object of custom type ZHENZHEN_SEEDANCE2_CONFIG - that second wire is the one you plug into any generation node's api_config input. A small frontend extension also drops a "注册… API ↗" button onto the node that deep-links to the right signup page for whatever channel you've selected.

Install

ComfyUI Manager → Install Custom Nodes → search Comfyui-zhenzhen, or:

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

then restart ComfyUI. No models download - everything runs server-side. But the pack's requirements are heavy for what you're using: aiohttp, openai, transformers, opencv-python, torchaudio and friends. The settings node itself barely needs requests; you're paying the dependency tax for the whole pack.

Where people get burned

The overseas zhenzhen channel is exactly that - overseas. The README is blunt: from mainland China you'll get 443 errors and need a VPN (the author recommends a Tun-mode client), and the fix is yours, not the pack's. On the generation side, HTTP 500s are usually the upstream vendor failing (the README names Sora/OpenAI as repeat offenders) - rerun rather than rebuild your graph. And since this is a reseller pack that puts your key in workflow JSON, don't share workflows with the key still in them, and only install it from the official repo. For one more opinion on the tradeoffs of API-wrapper packs, the KB's external-api-nodes.md essay is worth a read.