What is an AI video seed? How to repeat a result without one
A seed fixes a generator's random starting point. Sume's video models take none and refuse the field. How to keep a clip or a look without one.

An AI video seed is a number that sets the random starting point of a generation. On a generator that accepts one, sending the same seed with the same prompt and settings is meant to reproduce a result, and a new seed gives a new variation. Sume's video models don't accept a seed: each one reports seed: false, and a request that sends seed is refused.
So on Sume you keep a result by storing the clip, keep a look by pinning the first frame, and retry safely with an idempotency key. The facts below come from the Video generation docs and the API code, read on 2026-09-27.
What does a seed do in AI video generation?
It makes randomness repeatable. A generator draws random values to start each clip, and the seed picks which ones. Keep the seed and every other input the same, and a model that supports seeds is meant to produce the same output; change only the seed, and you get a different take of the same request.
Support varies. Sume's docs list seed in the request table as "Seed for deterministic generation (not guaranteed by all providers)", then note in their list of Sume differences that no video model accepts it.
Can I set a seed on Sume's video models?
No. In GET /v1/videos/models, every model reports seed: false, and POST /v1/videos refuses the field instead of ignoring it: today a request with seed returns 400 unsupported_parameter with the message “seed is not supported in v1 — every model reports seed: false.” Provider options are no way around it either, because allowed_passthrough_parameters is empty for every model and a non-empty provider.options is refused the same way.
The fix is to remove the field. Video generation API 400 errors covers the error body and the other refused parameters.
How do I get the same result again without a seed?
Decide what you need to keep, then hold that part fixed:
| To keep | Do this | Why it works |
|---|---|---|
| A clip you like | Store the finished file and reuse it. | Generated media is returned on media.sume.com, and those Sume-owned artifact URLs are the public contract. |
| The opening image | Send it in frame_images as the first_frame. | Frame images set the clip's first or last frame. |
| A character or style across shots | Reuse the same first frame or the same input_references. | See consistent characters across shots. |
| The model | Pin a model id such as seedance-2.5 instead of sume/auto. | sume/auto picks the model and does not disclose which. |
| One job when you retry | Resend with the same Idempotency-Key and the same body. | A replay returns the original job instead of a new generation. |
Does the same prompt give the same video?
Sume's docs make no such promise, and there is no seed to hold fixed. Treat each generation as a new take and keep the ones you want.
Resending a request with the same Idempotency-Key doesn't make a second take either: the replay returns the job you already have instead of generating again. More on keys in Idempotency keys for AI video APIs.
Sources
Related posts
More in Models
- An OpenRouter-compatible video API: sume/auto or a pinned model
Sume's POST /v1/videos follows OpenRouter's video generation API field for field. Let sume/auto pick the model, or pin a catalog id like seedance-2.5.
- Image generation API with reference images: POST /v1/images
Send a prompt plus public HTTPS reference images to Sume's POST /v1/images. Pin a catalog model or send sume/auto; the catalog lists each model's limits.
- Video 1.0 and Image 1.0 are retiring soon: move to sume/auto
Sume Video 1.0 and Image 1.0 are retiring soon and already run as aliases for the Auto path. New integrations call /v1/videos or /v1/images with sume/auto.
- Music generation API: the Sume Music Router with Lyria 3.5
Sume's Music Router turns a text prompt into a track via POST /v1/music-router/generate. sume/music-auto picks the engine, Lyria 3.5 today.
Written by Sume