The Adult Creator's API Stack: Every Endpoint You Need

You do not need five tools and a team. You need a handful of endpoints that fit together. Here is the exact Nureta API stack a solo adult creator runs — every call, in the order you use it, behind one key.

0. Auth — one bearer key#

Create a key on the keys page and pass it as Authorization: Bearer sk-.... Every call — create, poll, edit, upload — authenticates the same way and counts toward that key's rate limit (10 req/s default, adjustable 1–100).

1. Upload — POST /contents/uploads#

Get a short-lived signed URL, PUT your reference image straight to storage, and reference the returned assetUrl in tasks. Uploads are free; you are billed only on generation. This is how your recurring cast gets into the pipeline — pair it with reference images for consistent faces.

2. Models — GET /api/v3/models#

A public endpoint returning every model with live per-second and per-duration pricing: seahorse-480p/720p/1080p (managed) and seedance2.0-fast/pro (verbatim passthrough). Pick your resolution and cost profile before you spend.

3. Create — POST /contents/generations/tasks#

curl -s -X POST "$TOKENSTORE_URL/api/v3/contents/generations/tasks" \
  -H "Authorization: Bearer sk-..." -H "Content-Type: application/json" \
  -d '{ "model": "seahorse-480p", "duration": 8, "ratio": "9:16",
        "content": [
          { "type": "text", "text": "describe the shot" },
          { "type": "image_url", "image_url": { "url": "https://.../lead.jpg" } }
        ] }'

Text plus up to nine reference images and an audio track. duration 16–180 renders a stitched multi-shot scene. Full field reference: video API docs.

4. Edit — plan, structured, render, cancel#

• mode: "edit" drafts a storyboard you review before spending.
• PUT …/plan/structured edits each shot's action beat and re-expands it server-side.
• POST …/render renders the approved plan; POST …/cancel refunds a draft in full.

5. Poll or get called back#

GET …/tasks/:id returns a step object for live progress and, on success, content.video_url. Or skip polling entirely: pass a callback_url and the finished task is POSTed to you, HMAC-signed. The automation loop is in NSFW video API automation.

The stack is adult-native#

The whole stack runs the explicit pipeline: flag a shot explicit: true and it routes through anatomy references so the act renders concretely. That is the endpoint no mainstream API gives you — see rendering explicit sex acts on video.

What it costs to run#

Per-second video and per-image billing, USDC on Base, automatic refunds on failure. You pay for output, not seats. Try the whole stack visually first in the playground.

A studio used to be a building. Now it is six endpoints and a key — adult-native top to bottom, with nobody's filter in the middle.