☁️BizyAir Seededit3

This one's a little different from the rest of the pack. It doesn't load a model or run a local pipeline at all - it's a direct call to ByteDance's Doubao SeedEdit 3.0, a commercial image-editing API you'd otherwise need a separate Volcengine/ByteDance developer account to touch. BizyAir just proxies it, so you spend BizyAir credits instead of setting up billing with ByteDance yourself.

Worth knowing what you're actually calling: ByteDance runs a strict two-track policy with everything it ships. Components and research tools (Depth Anything, SDXL-Lightning, PuLID) go out free and open. Anything that's a product - and SeedEdit is squarely a product, sitting in the same closed Seedream/Seedance/Doubao family - stays API-only, forever. There's no local SeedEdit checkpoint to download and never will be; this node is the only way to reach it from inside ComfyUI.

What it does

Give it an image and a text prompt describing the edit you want, and it sends both to the Doubao SeedEdit model, which returns an edited version of the image. This is instruction-based image editing in the same broad category as Flux Kontext or Qwen-Image-Edit - you're not regenerating from scratch, you're asking the model to change something specific about an existing image while keeping the rest intact.

Inputs and outputs

Everything here is required, no optional inputs:

• image - the source image to edit.
• prompt - a multiline text field describing the edit.
• model - an enum, but as of this writing it only has one choice: doubao-seededit-3-0-i2i-250628. It's there for forward compatibility if BizyAir adds more Doubao variants later; right now it's effectively fixed.
• seed - ranges from -1 (random) up to 2147483647, standard fare.
• guidance_scale - a float from 1 to 10, defaulting to 5.5. This is the model's equivalent of CFG: higher pushes the output to follow your prompt more literally, lower gives the model more room to interpret.

It returns two outputs: image, the edited result, and bizyair_model_name, which just echoes back which model handled the request (useful mainly for logging or branching a workflow, not something you'll usually wire anywhere).

Installing BizyAir

Through ComfyUI Manager, search "BizyAir" and install. Or by hand:

cd ComfyUI/custom_nodes && git clone https://github.com/siliconflow/BizyAir.git

Restart ComfyUI afterward. Comfy-CLI works too: comfy node install bizyair. The step that actually matters for this specific node is the one after install - the README is blunt that you must set an API key on first use, via the "click to login" link. Since this node makes a live paid API call under the hood rather than running anything locally, a missing or invalid key isn't a warning, it's a hard stop.

Common issues

If nothing comes back, the API key is the first thing to check - this node has zero local fallback, so an auth problem just looks like a silent failure or a generic error, not something that points you at the actual cause.

Because it's a real commercial API and not open infrastructure, expect it to have its own content and usage policies layered on top of whatever your BizyAir account allows - a prompt or image that a locally-run editing model would happily process might get rejected here, and that's coming from ByteDance's side, not a bug in the node.

One more thing worth flagging honestly: as of this writing there's very little public discussion of this specific node anywhere in the ComfyUI community. It's a niche, recently-added entry point (the pack's changelog dates its BizyBot text-editing feature to mid-2025, and Seededit3 sits in that same "newer API integrations" wave), so if you hit an edge case, you may be one of the first people to document it.