Deprecated - MuAPI-only Character Sheet (Unsupported)

Let's get the important thing out of the way immediately: this node does not work, and it's not supposed to. Seedance2Character - displayed as "Deprecated - MuAPI-only Character Sheet (Unsupported)" - is a deliberately broken node. Run it and it raises an error telling you exactly that. It's kept in the pack for one reason only: so old workflows built against the original muapi.ai version fail loudly with a clear message instead of silently doing nothing.

Here's the backstory. This pack is a fork of Anil-matcha/seedance2-comfyui, which originally talked to Seedance 2.0 through a third-party service called muapi.ai. In that world, Seedance2Character was a real feature: it took reference photos of a character plus an outfit description and generated a character sheet. This BytePlus fork replaces muapi entirely with direct BytePlus ModelArk API calls - and BytePlus's Seedance video API simply has no character-sheet generation endpoint. So the node's functionality has no target to talk to. The author's choice, which I think is the right one, was to keep the node, hard-code it to fail, and point you at the replacement rather than delete it and leave old workflows mysteriously broken.

What it would have done

The schema still shows its old shape: outfit_description (a multiline string like "cyberpunk jacket with neon accents, glowing visor"), up to three reference images (image_1–image_3), an api_key, and outputs of sheet_image, sheet_url, and character_id. None of it functions against BytePlus. Don't reach for it.

What you should use instead

The fork's replacement is Seedance 2.0 Consistent Character Video. Same underlying goal - keep a specific character recognizable across generations - achieved the way the BytePlus API actually supports: you supply a reference image of the character (via sheet_image or sheet_url) and the generation node carries that identity through the clip. No sheet-building step involved; you bring the reference, it does the rest. That's also the direction the wider community moved in general: generate the character once, then keep referencing that artifact rather than re-deriving it.

The migration path for an old workflow:

Load Image → Seedance 2.0 Consistent Character Video sheet_image
Seedance 2.0 Consistent Character Video → (prompt, save, etc.)

If you have an old muapi workflow with a Seedance2Character node, the practical move is: delete it, wire your best character reference image into Consistent Character Video instead, and delete any node downstream that was consuming character_id - that concept doesn't exist on the BytePlus path.

Install

The node ships with the pack, so there's nothing extra to do: ComfyUI Manager → Install via Git URL → https://github.com/nnnnkatsu/seedance2-comfyui-byteplus, restart. Keeping the node installed is harmless - it only errors when you actually run it, and that error is doing you a favor.