From Script to Video: Handing Beats to the Storyboard
Turn a $0.01 adult script into a rendered video — how the script's scenes map to the video storyboard's segments and explicit flags on the Nureta API.
2 min read
A script is cheap ($0.01) and a video is not — so the smart pipeline is to write and refine the script first, then hand its beats to the video storyboard. The two APIs are built to connect: a script's scenes map cleanly onto the video's segments. This guide walks the handoff.
One director, two stopping points
The script API is the same v3 director the video path uses — it just stops after writing. So a script's scenes (each with a beat and a durationSeconds) are already in the shape the video storyboard wants: an ordered list of shots with per-shot text and length.
Scenes → segments
In the video API, a storyboard segment is { script, duration_seconds, explicit }. Take each scene from your script, use its beat as the segment script and its duration as duration_seconds, and submit them as a segments array. The segments must total 16–180s, which becomes the video length.
curl -s -X POST "$TOKENSTORE_URL/api/v3/contents/generations/tasks" \
-H "Authorization: Bearer sk-..." -H "Content-Type: application/json" \
-d '{
"model": "seahorse-480p", "ratio": "9:16",
"content": [{ "type": "text", "text": "carry the script's premise here" }],
"segments": [
{ "script": "scene 1 beat, build-up", "duration_seconds": 8, "explicit": false },
{ "script": "scene 2 beat, the explicit act described concretely", "duration_seconds": 12, "explicit": true }
]
}'Set the explicit flag per beat
Your script already separates build-up from payoff — carry that across as the explicit flag. Build-up beats are explicit: false (rendered from text); the act beats are explicit: true and route through the anatomy-reference pipeline. Spell out the act on the explicit ones; guidance in explicit scene beats that render.
Or refine in edit mode
Prefer to review before spending? Submit with mode: "edit" to get an editable storyboard draft, tweak each beat with the structured edit endpoint, then render. Cancel an un-rendered draft for a full refund. The modes are in the video API docs.
Why split it this way
- Explore premises at $0.01 before paying to render.
- Lock the structure in text, so the expensive render only happens on an approved plan.
- Keep characters consistent by pinning references at the video step — see character consistency in adult scripts.
Where to go next
Write the script first with one-line idea to adult script, pace it with build-up vs explicit beats. Field references: script and video API docs, plus your API key.
Render a script as video →