Sociaro

bytedance/seedance-2.0-fast

Seedance 2.0 Fast — the same request shape as Seedance 2.0, quicker and cheaper per token, capped at 720p.

Between the base model and Mini.

Slugbytedance/seedance-2.0-fast
Kindvideo
Vendorbytedance
EndpointPOST /v1/byteplus/contents/generations/tasks
ReferencesPOST /v1/generations/refs

Charged per job from what the generator reports it rendered — your Logs show the exact figure for each one; see balance and billing.

Calling it

curl https://api.sociaro.com/v1/byteplus/contents/generations/tasks \
  -H "Authorization: Bearer $SOCIARO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "model": "bytedance/seedance-2.0-fast",
        "prompt": "a paper boat on a rain-soaked street",
        "resolution": "720p",
        "duration": 5
      }'

# then poll the job id it returns:
curl https://api.sociaro.com/v1/byteplus/contents/generations/tasks/JOB_ID \
  -H "Authorization: Bearer $SOCIARO_API_KEY"

Parameters

Seedance 2.0 Fast — quicker and cheaper, same request shape

FieldTypeRequiredDefaultValuesWhat it does
contentarrayyes—parts, each with its own type and an optional roleThis is the whole input. `{"type":"text","text":…}`, `{"type":"image_url","image_url":{"url":…},"role":"first_frame"|"last_frame"|"reference_image"}`, `{"type":"video_url",…,"role":"reference_video"}`, `{"type":"audio_url",…,"role":"reference_audio"}`.
resolutionstringno720p480p · 720pA tier this model does not have is refused with a 400 naming the ones it does. The generator would ACCEPT it and silently render 720p, so the check is ours and it costs you nothing.
durationintegerno54–15, or -1Seconds. `-1` lets the model pick the length that suits the inputs.
ratiostringnoadaptive21:9 · 16:9 · 4:3 · 1:1 · 3:4 · 9:16 · adaptive
output_formatstringnomp4mp4`mov` exists on 2.5 alone.
generate_audiobooleannofalsetrue · falseSound is off unless you send `true`, on every route, except when you send your own audio (a `reference_audio` part) or set the field `omni_reference_task_type` to `edit` or `extend` (2.5 models only): then the generator's own default applies, and it is on. On the 2.0 models an edit or extension is asked for in the prompt, without that field, so it comes back silent unless you send `"generate_audio": true` or your own audio (`reference_audio`), with which sound is on by default. With `true` the clip gets generated sound synchronised with the picture, at the same price: these models are metered per token.
bitrate_modestringnothe model's ownstandard · highNot in the vendor's public reference, but the generator honours it: `high` encodes at a higher bitrate than `standard` (in one 480p measurement about 4.6–6.9 Mbps against 1.2–1.9 Mbps), and the price is the same, because these models are metered per token. The default differs by model, so leave it out to take the model's own.
return_last_framebooleannofalsetrue · falseAsks for the closing still beside the clip, at NO extra cost — useful as the `first_frame` of the next clip. The poll returns it as `content.last_frame_url`, the vendor's own link, with `last_frame_media_url` beside it: ours, on the same expiring terms as `media_url`.
watermarkbooleannofalsetrue · falseNo mark unless you send `true`, which puts an `AI Generated` mark in the lower right corner. `false` is the generator's own default: `/v1/byteplus` and `/v1/modelark` add no `watermark` to your body, so it applies there, and the other routes send `false` when you leave the field out.
seedintegernorandom—Every Seedance model we serve accepts it. The same seed gives similar, not identical, results: the vendor says complete consistency is not guaranteed.
execution_expires_afterintegerno1728003600–259200Seconds after submission at which the generator gives up on a task that has not finished and marks it `expired`. We charge only a finished clip, so an expired task costs you nothing, and the task stays pollable for its whole window. A value that is not a whole number in the range is refused before anything is created (`400`, `invalid_input` on `/v2/jobs`); `/v1/byteplus` and `/v1/modelark` forward it as sent and the generator refuses a bad one itself. On `/v2/jobs` the job still ends at its own `max_runtime_sec`.
safety_identifierstringno—1–64 charactersA fixed id for YOUR end user, one per user, which the generator uses to spot an end user who breaks its usage policy. We never send your value itself: we send a per-organisation pseudonym of your value (64 hex characters, the same for the same value on all your organisation's keys and routes), and the task reports that pseudonym back. A blank or longer value is refused before anything is created (`400`, `invalid_input` on `/v2/jobs`), on every route.

Worked example

curl https://api.sociaro.com/v1/byteplus/contents/generations/tasks \
  -H "Authorization: Bearer $SOCIARO_API_KEY" -H "Content-Type: application/json" \
  -d '{ "model": "bytedance/seedance-2.0-fast",
        "content": [{ "type": "text", "text": "a paper lantern drifting over still water" }],
        "resolution": "720p", "duration": 5 }'

# edit a clip: the clip to edit is a reference_video part, the picture of what goes in a reference_image; sound on asked for explicitly
curl https://api.sociaro.com/v1/byteplus/contents/generations/tasks \
  -H "Authorization: Bearer $SOCIARO_API_KEY" -H "Content-Type: application/json" \
  -d '{ "model": "bytedance/seedance-2.0-fast",
        "content": [
          { "type": "text", "text": "Replace the cat in [Video 1] with the lion from [Image 1]" },
          { "type": "image_url", "image_url": {"url": "https://your-cdn.example.com/lion.jpg"},
            "role": "reference_image" },
          { "type": "video_url", "video_url": {"url": "https://your-cdn.example.com/cat.mp4"},
            "role": "reference_video" }
        ],
        "resolution": "720p", "ratio": "16:9", "duration": 5, "generate_audio": true }'

# extend: join three clips with generated transitions (duration is the length of the clip you get back); sound on asked for explicitly
curl https://api.sociaro.com/v1/byteplus/contents/generations/tasks \
  -H "Authorization: Bearer $SOCIARO_API_KEY" -H "Content-Type: application/json" \
  -d '{ "model": "bytedance/seedance-2.0-fast",
        "content": [
          { "type": "text", "text": "The window in [Video 1] opens and the camera moves inside, transitioning into [Video 2], then into the painting, transitioning into [Video 3]" },
          { "type": "video_url", "video_url": {"url": "https://your-cdn.example.com/1.mp4"},
            "role": "reference_video" },
          { "type": "video_url", "video_url": {"url": "https://your-cdn.example.com/2.mp4"},
            "role": "reference_video" },
          { "type": "video_url", "video_url": {"url": "https://your-cdn.example.com/3.mp4"},
            "role": "reference_video" }
        ],
        "resolution": "720p", "ratio": "16:9", "duration": 8, "generate_audio": true }'

Same request shape as Seedance 2.0, quicker and cheaper per token — between the base model and Mini. Use it when Mini is not quite enough and the base model is more than you need.

480p and 720p only. Ask for 1080p or 4K and you get a 400 naming the two you can have. That check is ours: the generator would accept the value, ignore it, hand you 720p and bill you for it.

Metered per token like the other two, with the same minimum cost on video-input jobs.

Editing and extending a clip. Neither has a field or a role of its own. Both are ordinary requests: the clip goes in content as a reference_video part, and the model works out from your prompt what to do with it. omni_reference_task_type does not help here, because this model accepts it and ignores it. Both examples above show the shape.

  • Edit: replace, add or remove something in a clip, or redraw part of it. Send the clip, plus a reference_image or reference_audio part for anything new it needs. Describe what to add, where and when; to remove something, also say what must stay unchanged.
  • Extend: continue a clip forward or backward, or send two or three clips and have the gaps between them filled. A forward or backward extension usually keeps only the tail of the original clip, so ask for the original in the prompt if you want it (for example, "… and then end with [Video 1]"). Two or three clips come back with the originals and the new footage joined.
  • Name each clip [Video 1], [Video 2] in content order, not "reference Video 1": the generator's own guide warns that the word "reference" can make it treat the clip as something to imitate rather than the clip to edit.
  • Clips: up to 3, each 2–15 s and 15 s in total, mp4 or mov, up to 200 MB, 24–60 fps.
  • duration is the length of the clip you get back (4–15, or -1). The generator does not say for this model whether duration means the length of the addition instead (our 2.5 page documents that reading for 2.5), nor whether an edit keeps the original clip's soundtrack.
  • Price: the same as any job with a video input. At the standard rate on /v1/byteplus and /v2/jobs the minimum at 720p is about $0.67 for a 5 s output, $0.89 for 8 s, and $0.59 for 4 s (the routes that prepare your files first, /v1/generations/refs and /v1/modelark, are priced separately); with -1 or no duration it is the figure for the length the generator chose, as it reports it (4 s if it reports none). A render that meters more is charged what it meters.

How a job runs

These routes are a pass-through: you send BytePlus's own body and get their own response back, with our additions beside it. Generation takes longer than a request should wait, so it goes in three moves — submit, poll, collect.

# 1. submit — the id comes back as `id`. There is NO `job_id` on THIS response
curl -sS https://api.sociaro.com/v1/byteplus/contents/generations/tasks \
  -H "Authorization: Bearer $SOCIARO_API_KEY" -H "Content-Type: application/json" \
  -d '{ "model": "…", "content": [ … ] }'
# -> { "id": "cgt-…" }

# 2. poll every 5-10 s
curl -sS https://api.sociaro.com/v1/byteplus/contents/generations/tasks/cgt-… \
  -H "Authorization: Bearer $SOCIARO_API_KEY"
# -> { "status": "running", … }
# -> { "status": "succeeded", "content": { "video_url": "<the vendor's own link>" },
#      "media_url": "https://api.sociaro.com/v1/media/<media_id>" }

# 3. collect — the opaque id IS the credential, no header needed
curl -sSL "https://api.sociaro.com/v1/media/<media_id>" -o out.mp4

Images use POST /v1/byteplus/images/async and its poll in the same shape, and the faster models also answer synchronously at POST /v1/byteplus/images/generations — one request, the picture in the response. A model whose render outlasts the gateway's ~2-minute ceiling is refused there by name, telling you to use the async route.

Reading the poll

Two differences will bite a client written against the poll-style routes. The SUBMIT returns id, not job_id — code reading job_id there gets nothing and cannot poll at all. And status is the VENDOR'S vocabulary: running, succeeded, failed — not processing, completed, failed. A check for completed on this route never becomes true, which reads as a job that never finishes rather than as an error.

The POLL response does carry job_id beside the vendor's id, as a convenience, and it returns the vendor's whole body — around twenty fields — rather than the five-field shape the other routes use. Gate on status rather than on the poll's HTTP code.

Prefer media_url over the vendor's raw link. Both are returned: content.video_url (or data[].url for images) is theirs, kept for compatibility and due to be removed once nobody reads it; media_url is ours. Ours points at our host, hides the vendor's storage, and expires. A second asset arrives on the same terms — return_last_frame gives content.last_frame_url with last_frame_media_url beside it.

Collecting the result

media_url is a capability: the opaque id is the credential, so no Authorization header is needed and anyone holding the link can fetch it. It expires within the hour — download rather than store the link.

Rules the gateway adds

Your key must be granted this model — 403 otherwise — and either spelling satisfies the grant: our catalogue id or the vendor's own native one.

Because this is a pass-through, unknown fields go to the generator rather than being refused here, and it is the generator that decides. The exception is resolution, which we check ourselves: an unsupported tier is silently ignored upstream, so you would ask for the higher one, be handed a lower one, and be charged. A tier we cannot price is refused at submit, before any money is spent, with a message naming the ones this model has.

Ranges and enums are the generator's own, so an out-of-range value comes back as its rejection, in its wording and with its numbers.