๐ Seedance 2.0 API Key
When to bother with Seedance 2.0 API Key
- api_key
Seedance 2.0 is ByteDance's closed-source video model - there are no weights to download, so the only way it shows up inside ComfyUI is through an API node like this pack. Every generation node in nnnnkatsu/seedance2-comfyui-byteplus needs your BytePlus ModelArk API key somewhere, and Seedance 2.0 API Key is the simplest way to supply it: one field, one output, done.
Except you probably shouldn't reach for it. The pack's own README calls it the "legacy key-only node," and the recommended entry point is Seedance 2.0 BytePlus Config, which carries the endpoint ID as well as the key. If you wire this one into a generation node, you still have to supply endpoint from somewhere else - a config node, an environment variable, or the config file. The key-only node only makes sense in workflows where the endpoint is already handled elsewhere and you just want the credential in one tidy box.
How it works
The mechanism is about as un-mysterious as it gets. You paste your BytePlus ModelArk API key into the api_key widget (tooltip: "Your BytePlus ModelArk API key") and the node hands it back out of the api_key STRING output. Nothing leaves your machine; the key is only sent when a generation node actually calls the API.
Here's the sneaky bit: the node doesn't blindly pass through your widget text. It runs the key through the pack's shared _load_api_key resolution, which checks, in order, the node field, the ARK_API_KEY environment variable, and a local config file at ~/.byteplus/seedance2-comfyui.json. That means you can leave the widget blank and let the environment provide the key - handy if you share workflow JSON around and don't want a key baked into the file. Saved ComfyUI workflows do include widget values, so this is genuinely the safer habit.
The one input, and where it goes
Only api_key matters, and its output feeds the api_key input of any generation node in this pack - Seedance 2.0 Text-to-Video, Image-to-Video, Omni Reference, Consistent Video, Extend, and the retrieval nodes. That input is optional on all of them precisely because of the env-var and config-file fallbacks, so a config node isn't strictly mandatory either.
Install and a word of caution
Install it with the rest of the pack - ComfyUI Manager โ Install via Git URL โ https://github.com/nnnnkatsu/seedance2-comfyui-byteplus, then restart. No model downloads, no GPU requirement; boto3 is only needed for the S3 helper nodes.
Security is the part worth taking seriously. An API node is the one shape of custom node that should phone home with your key, which is exactly what makes this category attractive to attackers - the ecosystem has been burned once already. Prefer this widely-shared pack over a random one-node key-collector, and treat the key as a secret: don't commit workflows with it, use a limited IAM/API credential where you can, and rotate. Honestly, Seedance 2.0 BytePlus Config does everything this node does and more, so use that. This one is the fallback, not the start.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| api_key | STRING | Your BytePlus ModelArk API key |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| api_key | STRING | โ |