NSFW AI Video API 2026: Flux 3, H3, Seedance & LTX Compared
Start From the Constraint, Not the Price
Most roundups sort by rate. That ordering is already published — per-second rates, the token formulas behind them and the full conversion tables are in AI Video Model Pricing 2026. It also answers the wrong question first.
Your binding constraint is rarely budget. It is whether the output is explicit at all, then a resolution ceiling, a duration ceiling, or a reference stack. Clear the constraint, then read the rate. Reversing that order is how the cheapest rate in the pool ends up attached to a job that endpoint cannot do.
The Decision Path
Answer one question before any other: is the output explicit? That fork decides which half of the pool you are in, because no parameter moves an endpoint across it.
Your binding constraint | Endpoint | Config to name | Moderation shape |
Explicit, cost is the constraint | lightricks/ltx-2.3-22b-t2v | 720p / 24fps | none |
Explicit, above 1080p | bytedance/seedance-2.0-t2v-spicy | 4K | none |
Explicit, driven from reference material | bytedance/seedance-2.0-ref2v-spicy | per-tier rate not published | none |
Not explicit, 2K with native stereo | minimax/minimax-h3-t2v | 2k, the only tier | light |
Not explicit, a moderation parameter per request | black-forest-labs/flux-3-t2v | 720p or 1080p, same price | caller-set |
Not explicit, 30 seconds in one call | bytedance/seedance-2.5-t2v | 720p | general-purpose, no spicy variant |
Every t2v row has an i2v sibling at the same rate. Two rows carry a caveat. The reference-driven Spicy endpoint is live, but its per-tier rate is not published, so budget it from a test call rather than by analogy. And Seedance 2.5's 30 seconds is real and unmatched here — 30 seconds of a general-purpose model, though, is not 30 seconds of an explicit one (what 2.5 is good at instead). Once LTX 2.3 is the pick, writing for it: the LTX 2.3 NSFW prompt guide.
Four Moderation Shapes, Not Two
"Uncensored or not" is the wrong axis. Four shapes ship today:
Moderation shape | Endpoints | Cheapest named config | Rate |
None | lightricks/ltx-2.3-22b-{t2v,i2v} | 720p / 24fps | $0.0391/s |
None | bytedance/seedance-2.0-{t2v,i2v,ref2v}-spicy | 480p | $0.084/s |
Light | minimax/minimax-h3-{t2v,i2v,ref2v} | 2k, the only tier | $0.260/s |
Caller-set, integer 0–4 | black-forest-labs/flux-3-{t2v,i2v} | 720p or 1080p, same price | $0.260/s |
General-purpose, no spicy variant | bytedance/seedance-2.5-{t2v,i2v,ref2v} | 480p | $0.134/s |
Read the last column against the first. At a matched 720p, LTX 2.3 bills $0.0391 per second at 24fps and Seedance 2.0 Spicy $0.1815, against $0.260 for Flux 3 — 6.6× the cheapest. Looser moderation is not a premium in this pool. Tier-by-tier rates for the explicit pair: MiniMax H3 NSFW.
Flux 3 is the only endpoint that hands the caller a moderation parameter: safety_tolerance, an integer from 0 to 4. That is a range the API documents, not a mapping from values to outcomes, and this article does not supply one. What that switch does and does not settle: Flux 3 vs MiniMax H3. H3 moderates lightly for a general-purpose model, but lightly is not the same as not at all.
Coming Soon to the Pool
Three models are named but have no callable endpoint on Siray today: Wan 3.0, Wan 3.0 Spicy and Wan 2.7 Spicy. Plan as though they are absent — the first two publish no spec at all, the third publishes a spec with no product page behind it. Nothing in the tables above changes while that holds.
FAQ
What is the cheapest NSFW video endpoint on Siray?
lightricks/ltx-2.3-22b-t2v at 720p/24fps, $0.0391 per second. It is unmoderated and stops at 1080p/30fps, 6 to 20 seconds — accepting that ceiling is what buys the rate.
Can Flux 3 or MiniMax H3 generate explicit video?
Neither is an adult endpoint. H3 moderates lightly for a general-purpose model, and Flux 3 exposes a safety_tolerance integer from 0 to 4 — a documented range, not a promise about any specific output. For explicit work the purpose-built endpoints are Seedance 2.0 Spicy and LTX 2.3.
Is Seedance 2.5 an NSFW option?
No. It is live, and it is the only model here that runs 30 seconds in one call, but it has no -spicy variant; ByteDance's explicit line is Seedance 2.0.
Summary
Sort by constraint, not by rate. Explicit work has three endpoints and two of them are the cheapest in the pool; everything else is a general-purpose model whose moderation shape you should name before you budget against it.
Get Started
Create your free Siray account and reach every endpoint above with one key — test the config your job actually needs before committing budget.
Compliance: Siray refuses all illegal content and enforces zero tolerance for CSAM. Every endpoint above is intended for lawful adult content involving consenting adults only, and never for a real person's likeness without documented consent. "Uncensored" and "Spicy" mean no excess filtering within the law — not the absence of it.