Automate Adult Video Production With an API

A production pipeline on the Nureta Developer API usually has five stages. Stage 1, ideation: turn a premise into a structured script. Stage 2, assets: upload or generate reference images. Stage 3, render: create a video task from the script. Stage 4, review: optionally park the storyboard for a human to approve. Stage 5, delivery: receive the finished video URL by webhook and publish it in your own product. Every stage uses the same bearer API key and the same create, poll, terminal task lifecycle, so one small worker service can drive the whole chain.

The key design choice is to treat every generation as a durable job, not a blocking HTTP call. Rendering a one-minute scene takes minutes, so your code should submit, store the task id, and move on. That makes the pipeline restartable: if a worker crashes, the task keeps running on Nureta's side, and your queue still knows which id to check.

Start with script generation, which is the cheapest stage by far. POST /api/v3/contents/scripts with {"model":"seahorse-script","content":[{"type":"text","text":"a late-night reunion between two former partners"}],"duration":60} costs a flat $0.01 regardless of length. The result carries a title, character names and a list of scenes, each with a setting, a beat and durationSeconds. The duration parameter (5–180 seconds) scales how many scenes you get, not the price.

Those scenes map almost directly onto a video storyboard. Take each beat, decide whether the shot is build-up or payoff, and pass them as segments[] with their own duration_seconds (4–15) and explicit flag. For references, POST /api/v3/contents/uploads returns a short-lived signed URL; you PUT the image bytes to it and reference the returned assetUrl in the task. Uploading is free, but presigning is capped at 30 requests per minute per key, so batch uploads accordingly.

Submit renders from a queue worker with POST /api/v3/contents/generations/tasks and persist the returned id immediately, before anything else can fail. The price is reserved from your balance at creation, so a successful submit means the job is funded. If an HTTP call times out and you are unsure whether the task was created, check your records and the task list before resubmitting; blind retries are how pipelines pay twice.

For tracking, each video task exposes a step object. Codes include queued, generating_script, generating_visuals, rendering (with done and total clip counts), stitching, done and failed. Map them to your own labels, since the API never sends display text. Polling works, but every request counts toward the key's rate limit (10 requests per second by default, adjustable from 1 to 100), so at volume webhooks are the better default.

Set callback_url on each task and Nureta posts the terminal task object, identical to what GET returns, to your HTTPS endpoint when the task succeeds or fails. Add callback_secret (8–256 characters) and verify each delivery: compute HMAC-SHA256 over the timestamp header, a dot, and the raw request body, then compare it in constant time with the signature header. Reject anything that doesn't match.

Build the receiver to be boring and idempotent. Delivery is at-least-once with up to 5 attempts, so deduplicate by task id. Return any 2xx within 5 seconds and do the heavy work (downloading, transcoding, publishing) asynchronously, because slow responses count as failures and redirects are not followed. Callback URLs must be HTTPS and cannot point at private or loopback addresses. Keep a slow polling sweep as a safety net for anything a webhook missed.

Full automation is fine for low-stakes volume, but for anything you publish under your brand, add a review gate with edit mode. Submit with "mode":"edit" and the task is charged, drafts a storyboard, and parks at status planned with a character preview, per-shot scripts, durations, explicit flags and people-free background previews. A reviewer can change beats or frames, then call POST …/tasks/:id/render, or POST …/tasks/:id/cancel for an immediate full refund. Drafts nobody renders are refunded automatically.

Automation doesn't move compliance off your plate. Everything generated through the Nureta Developer API is subject to Nureta's content policy: adults only, no minors including fictional ones, no real people without consent, no public figures, no non-consensual content. If your pipeline serves end users, age-gate them yourself and record consent for any reference photos they supply before those photos ever reach a task.

API pricing is per second of video from a prepaid balance: $0.1888 per second at 480p, $0.2773 at 720p and $0.5428 at 1080p. A worked example: 50 one-minute scenes at 480p cost 50 × 60 × $0.1888 = $566.40, plus 50 script drafts at $0.01 = $0.50, plus 100 reference images at $0.05 = $5.00, for a total of $571.90. Failed generations are refunded automatically, so the realistic cost is at or below that figure.

The prepaid model is also your circuit breaker. When the balance can't cover a new task, the API returns AccountOverdueError instead of queuing unbounded spend, so a bug that loops on task creation stops when the balance runs out. Keep this separate from the consumer Nureta app, which charges $1.29 per 5-second 480p video in USDC and is built for one person making one film, not for pipelines.