Qwen Image Edit Spicy · Image Editing

There are three inputs on this node. One image, one instruction, one seed. That's it. No mask, no strength dial, no aspect ratio, no resolution tier, no prompt expansion to forget to turn off. It is the simplest node in the entire SpicyAPI pack by a wide margin, and the description of it is refreshingly honest about what it does not offer.

It's also the one the vendor labels uncensored. Which is worth a paragraph, because "uncensored" on an API node means something specific. Moderation follows the model, not the node - a hosted closed model refuses what its vendor refuses and no node pack can patch that. Here, though, you're on a fine-tune of an Apache 2.0 editor: Apache 2.0 carries none of the anti-circumvention terms that made NSFW derivative work for Flux Kontext a licence violation, which is exactly why an open LoRA and fine-tune ecosystem grew around the Qwen Edit line in the first place. So the claim is plausible in a way the same claim would not be on, say, a Nano Banana node. It's still the vendor's claim, and it's still somebody else's servers logging your uploads.

The inputs

• image_url - an IMAGE socket. One image, the thing you're editing. It gets uploaded to SpicyAPI when the node runs, so treat that as part of the decision.
• prompt - describe the desired changes, in plain English. Since the model has no mask, the sentence is doing all the work of telling it what to leave alone; be explicit about the parts you're not changing.
• seed - optional, and useful. Same seed and settings, same result, so with a seed set you can change one word in the prompt and compare two edits rather than look at two unrelated pictures. That's a genuine advantage over nodes with more knobs.

The output

images and task id. Standard IMAGE, so Save Image next; the task id is what support wants when something fails.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/spicyapi-ai/comfyui-spicyapi

Restart ComfyUI and you're most of the way there. This pack adds no Python dependencies and downloads no weights - it's a client for a hosted service, so it runs on anything from a MacBook to a CPU-only box. Then take a key from spicyapi.ai/console/keys into Settings > SpicyAPI, restart once so the node list is built from your account, and go. Servers should set SPICY_API_KEY in the environment; either way the key stays out of your workflows and out of saved image metadata.

What to expect

It edits the frame, so the frame moves. No pinning of untouched pixels, no mask to fence the model in - that's the trade for having no options. If you need exact preservation of an area, this is the wrong node; use the 2.1 edit node with its mask_url input, white for the repaint region, black for what stays.

Chains of edits wear the face down. Run the same portrait through three passes and you'll have three slightly different people. Fewer passes, tighter instructions.

About $0.038 an image, so passes are the cost driver. A four-pass edit session to nail one picture is fifteen cents - fine, until it's a shoot of forty photos. Set Max cost per run in the SpicyAPI settings so the node quotes each run and refuses anything over your ceiling before charging.

Cancelling stops you waiting, not the job. The task finishes on SpicyAPI, is charged if it succeeds, and its result sits in your console for up to 14 days. Errors are pack-wide and code-based: No SpicyAPI key is set is self-explanatory, 40310 means the account's email is unverified, 40004 means no deployment serves the options you picked.