🌱 Seedance 2.0 BytePlus Config

If you're using this pack at all, this is the first node you should drag onto the canvas. The README is blunt about it: "Recommended first node." Seedance 2.0 BytePlus Config holds the two things every generation node needs - your BytePlus ModelArk API key and your endpoint ID - and hands both out of one tidy node, so you set them once and forget them.

Why does this even exist? Seedance 2.0 is ByteDance's flagship video model and it is closed, full stop. ByteDance's posture across the whole Seedream/Seedance line is API-only - you can't download these weights no matter how good your GPU is (for the record, the same company happily open-sources the components around it; the products stay on the API). So a workflow built with this pack is a cloud-call workflow: your prompt and images leave the machine, get rendered on BytePlus's servers, and come back as a video URL. The config node is just the credential plumbing for that deal.

The two fields that matter

• api_key - your BytePlus ModelArk API key. Tooltip: "Your BytePlus ModelArk API key."
• endpoint - the BytePlus ModelArk endpoint ID, like ep-.... Tooltip: "BytePlus ModelArk endpoint ID, for example ep-..."

That endpoint ID is worth a moment's understanding. Internally, this fork sends it to the official API field named model - it's how BytePlus knows which Seedance deployment to route to. If you have multiple endpoints (say, different resolution tiers), you can use separate config nodes per workflow. There's no base_url widget here, but the pack will honor the BYTEPLUS_ARK_BASE_URL environment variable if you ever need to point at a different region or proxy.

The node outputs both values as plain STRINGs, api_key and endpoint, and you wire them into the matching optional inputs on any generation node. It's also happy to run with blank fields: the pack's shared resolution checks the node widget, then the ARK_API_KEY / SEEDANCE2_ENDPOINT env vars, then a local config file at ~/.byteplus/seedance2-comfyui.json. So you can paste keys into the file or the environment and leave every widget empty - which keeps your credentials out of saved workflow JSON.

Install and the honest tradeoffs

Install via ComfyUI Manager → Install via Git URL → https://github.com/nnnnkatsu/seedance2-comfyui-byteplus, restart, done. No model files, no VRAM, boto3 only matters if you use the S3 helpers.

Two things to keep in mind before you fall in love. First, cost: every generation is a paid API call, and Seedance pricing adds up fast - the community reaction to Seedance landing in ComfyUI as an API was largely sticker shock. Second, your inputs are moderated by ByteDance's servers and subject to their content policy; you can't abliterate a closed model. That's the price of a model you were never allowed to download. Use BytePlus Config, run a cheap test clip at 480p, and check the meter before you batch ten 4K renders.