● nureta

Rendering Explicit Scenes on AI Video (Not Just Suggestion)

How the explicit flag and anatomy-reference pipeline render adult scenes on AI video, and how to prompt position, contact and motion so they work.

Updated · 4 min read

There is a gap between an AI clip that hints at sex and one that actually shows it. Most generators land on the first: two bodies close together, some motion, everything left to the imagination. Nureta is built to close that gap and render the act itself as concrete on-screen motion — for fictional, consenting adults, within Nureta's content policy.

The mechanism is the explicit flag and the anatomy-reference pipeline behind it. This guide explains what that pipeline does, and — more importantly — how to prompt so it has something real to render.

Why most AI video only suggests

The base video model has no built-in understanding of sex acts or human anatomy under load. Ask it for a couple having sex and it does the safe thing it knows how to do: it renders two people moving near each other. The result reads as intimacy but never resolves into an act. That soft, suggestive motion you have seen everywhere is a knowledge gap, not a censorship setting.

What the explicit flag does

When a shot is flagged explicit, Nureta routes it through a dedicated anatomy-reference pipeline before rendering. That pipeline attaches real anatomy references for the act you described, so the model renders the act concretely instead of guessing. Character identity, skin markings and tattoos stay consistent through the shot, so the explicit render still looks like the same person.

The explicit flag is not a permission switch — what may be generated is set by the content policy either way. It only decides whether a shot gets anatomy references. A build-up shot (a look, undressing, afterglow) should stay explicit: false so sex does not bleed into a moment that is not about sex yet.

Describe the act, concretely

The pipeline can only reference what you name. An explicit shot with a vague line like they get closer produces no useful references and renders soft — the flag alone does nothing. Spell out three things: the position, the point of contact, and the motion.

  • Position — who is where: woman on top, man behind her, standing, side by side on the bed.
  • Contact — state it plainly rather than implying it: his hands on her hips, bodies pressed together.
  • Motion and pace: slow, building rhythm, faster toward the end — motion is what separates a still from an act.

Weak: a couple having sex on a bed. Strong: low-angle close shot, adult couple on a bed, woman on top, slow rhythm building faster, both nude, warm lamplight.

Auto mode flags it for you

By default (mode: "auto") you never touch the flag. Describe the scene in one prompt and the director decides which shots depict sex and flags them for the anatomy pipeline automatically. This is the right path for most single clips — you write what happens, the platform handles the routing. Start here; the full single-clip walkthrough is in how to create an NSFW video from a prompt.

Advanced mode: set explicit per shot

For a multi-shot scene where you want to decide exactly which beats are explicit, use advanced mode: pass your own segments array and set explicit: true on the shots that show sex. Each segment carries its own script and duration, and explicit shots must spell out the act in that script. Whatever you set overrides the director's guess. See the storyboard modes docs for the full segment shape, and multi-shot adult scenes for pacing a longer render.

Calling the API

In auto mode you send one text item and let the director flag the explicit beat. Create the task, then poll for the video URL.

curl -s -X POST "$NURETA_URL/api/v3/contents/generations/tasks" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "seahorse-720p",
    "duration": 10,
    "content": [
      { "type": "text", "text": "low-angle close shot, adult couple on a bed, woman on top, slow rhythm building faster, both nude, warm lamplight" }
    ]
  }'

Every field, plus polling and webhooks, is in the generation API docs.

Mistakes that render soft

  • Flagging a shot explicit but describing it vaguely — no references get built, so it renders soft anyway.
  • Naming no motion: she sits on him is a pose; she moves on top of him, slow then faster is an act.
  • Flagging build-up shots explicit — sex bleeds into a shot that should be a look or a touch.
  • Fighting the model for permission — there is nothing to jailbreak; every model here is adult-native, and the content policy is the only boundary.
Open the playground →