Z-Image Spicy Pro: What's Confirmed Before It Lands on Siray

Z-Image Spicy Pro is queued for Siray's NSFW model lineup — it isn't callable through Siray's API yet. Before it lands, here's what's actually confirmed about the spec, what carries over unchanged from Z-Image (turbo), and what's still genuinely unknown. Nothing below should be read as "available today."

Key Takeaways

• Z-Image Spicy Pro adds a higher resolution ceiling (up to 2560px) and a prompt_extend param — a real step up from Z-Image (turbo).
• It carries over turbo's two boundaries unchanged: no negative_prompt field, no face-swap capability.
• No confirmed launch date and no confirmed Siray price yet — the vendor's own listed rate is not Siray's rate.

What's New Compared to Z-Image (Turbo)

Two things separate the Spicy Pro tier from the turbo model Siray already offers, per the vendor's own API documentation (MuleRouter). Width and height both run 256–2560px, defaulting to 1024×1024 — a materially higher ceiling than turbo's default. The second addition is prompt_extend, a boolean parameter (default false) that auto-rewrites and expands your prompt before generation, useful for short prompts that need more descriptive detail filled in automatically.

In practice, prompt_extend earns its keep in two specific situations: a short, quickly-typed prompt ("woman in red dress, city street at night") that needs the model to fill in lighting, composition, and material detail on its own, or a batch-generation workflow where writing a fully art-directed prompt for every single request isn't worth the time. The tradeoff runs the other way for prompts that are already fully specified — a prompt with an exact camera angle, lighting setup, and style reference gets less benefit from expansion, and turning prompt_extend on by default for every request risks the model reinterpreting details you'd already locked in. Leaving it at its default false and switching it on selectively, rather than as a blanket setting, is the safer starting point once the endpoint is live.

Why the Higher Ceiling Matters

The jump to a 2560px ceiling isn't just a bigger number on a spec sheet — it changes what the output is actually usable for. Turbo's default resolution is built for typical single-post social content, where a moderate size is more than enough and a bigger file just means slower generation and upload for no visual benefit. A 2560px ceiling opens up larger formats: print-adjacent posters, hero banners, or any placement where the image gets displayed bigger than a phone screen and needs to hold detail at that size. If a pipeline only ever ships square social posts, the higher ceiling may not change day-to-day output much — but for anyone producing larger-format pieces, it's the more consequential of the two confirmed additions, more so than prompt_extend.

What Carries Over Unchanged

Two boundaries stay exactly where they are on Z-Image (turbo) today — the Pro tier doesn't touch either one. There's no negative_prompt field on this endpoint, matching turbo's existing gap; if your workflow depends on exclusion lists, this tier won't add one. There's also no face-swap or identity-transfer capability. This isn't a new restriction introduced with Pro — it's the same two limits creators already work around on turbo, just confirmed to still apply here.

What Isn't Confirmed Yet

Two things are genuinely still open, and worth naming plainly rather than guessing at. There's no confirmed launch date beyond "coming soon" — plan around that, not around a specific day. And there's no confirmed Siray price: the vendor's own documentation lists a rate for its own API, but that figure belongs to the vendor, not to Siray's console. Siray sets its own pricing once an endpoint actually goes live, and it's often not a straight pass-through of the upstream rate.

What to Do Now

If Z-Image (turbo) is already in your NSFW pipeline, the practical move is to plan your prompt structure for the resolution jump now, rather than wait and rewrite later. A prompt built for turbo's default square output likely needs adjusted framing language for taller or wider Pro-tier outputs. Beyond that, there isn't much to prepare — no sandbox exists yet, and no example generation from this specific endpoint can be shown honestly until it's live.

It's also worth doing a quick inventory of current output now, while there's nothing else to prepare: which pieces are square social posts, where the resolution jump changes little, versus larger-format pieces, where it matters directly? That distinction is what determines whether Spicy Pro is worth switching to as soon as it lands, or something to adopt selectively for specific outputs while keeping turbo as the default for routine social content.

Check the model list at console.siray.ai/model-api for the moment Z-Image Spicy Pro actually appears — that's the confirmation point, not this article. In the meantime, the turbo tier already covers character consistency and general NSFW prompt structure; see Z-Image NSFW Prompt Guide: Uncensored Tips and Z-Image NSFW Character Consistency: Keep the Same Face for techniques that should carry over directly once Pro lands.

Create your free Siray account now and you'll be set up to try Z-Image Spicy Pro alongside 300+ other models the moment it goes live.

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. Z-Image Spicy Pro, once live, will be a third-party model available through Siray's API, not a Siray-hosted model, and the same standard will apply to everything generated with it.