Consistent Outfit Changes with Seedream 5.0 Pro Spicy i2i

bytedance/seedream-5.0-pro-i2i-spicy, available through Siray's API, edits an existing image rather than generating one from scratch. Its i2i request adds exactly one field beyond the model's bare-minimum t2i shape: images*, an array. That one field is what makes batch outfit changes on the same character possible — feed it a clear reference of the character each time, vary only the outfit description in the prompt, and run the call again.

Key Takeaways

• Seedream 5.0 Pro Spicy has no seed field — there's no shared seed to hold a character constant across a batch. Consistency comes from what you put in images, not from reproducibility.
• Pricing is flat: $0.045/image, regardless of resolution requested.
• images has no documented size limit in Siray's spec — treat it as an open array, not a fixed slot count.

The i2i Endpoint's images Array — Not ref2i

There's no ref2i endpoint on Seedream 5.0 Pro Spicy — that naming belongs to a different model, Seedream 4.5 Spicy. What Seedream 5.0 Pro Spicy has is simpler: its i2i request takes model, prompt, size, output_format, and images* — one array field carrying whatever reference image(s) you want the edit anchored to. Pricing is flat at $0.045/image no matter the resolution requested, and size offers 16 values spanning 8 aspect ratios (1:1, 4:3, 3:4, 16:9, 9:16, 3:2, 2:3, 7:3) at two resolution tiers, up to 3136x1344.

Why Consistency Comes From the Reference, Not a Seed

This model has no seed parameter at all — every call is an independent generation, with no way to reproduce a prior result exactly, only re-roll. For a single edit, that's a minor inconvenience covered in Siray's Seedream 5.0 Pro Spicy i2i editing guide. For a batch of outfit variants on the same character, it matters more directly: you can't rely on a shared seed to keep the character's face and build stable across four or five separate calls. Instead, consistency comes entirely from the images array — feed the same clear reference image (or images) of the character into every call in the batch, and change only the outfit/scene portion of the prompt each time.

Running a Batch

For each variant, keep the character description and the reference image(s) in images identical across calls; change only the outfit and scene description in prompt. Four outfit variants at $0.045/image runs $0.18 total — cheap enough to iterate on which reference image actually holds the character most consistently before committing to a full batch. If an early result drifts from the character, that's usually a sign to swap in a cleaner, more front-facing reference image, not to fight it with more prompt detail.

When ref2i on Seedream 4.5 Spicy Fits Better

If the goal is closer to "generate a brand-new scene using this character as a reference" rather than "edit this specific image," Seedream 4.5 Spicy's actual ref2i endpoint (bytedance/seedream-4.5-ref2i-spicy) is the better-suited tool — it's built for reference-to-image generation, not editing. Seedream 5.0 Pro Spicy's images array is for editing an existing shot, not composing a new one from a reference.

Developer Notes

Both run through the same normalized API Siray exposes across its catalog, so switching between an editing workflow and a reference-generation workflow is a model swap, not a new integration.

Ready to batch your first character's wardrobe? Create your free Siray account and try Seedream 5.0 Pro Spicy's images array.

A Note on Compliance

Siray's own NSFW and uncensored models generate legal, consensual adult content only — CSAM and any illegal content are refused with zero tolerance. "Spicy" means no moderation beyond what the law requires, not that anything goes. Seedream 5.0 Pro Spicy is a third-party ByteDance model available through Siray's API, not a Siray-hosted model, and the same standard applies to everything generated with it.