Does sume/auto pick a different video model on a retry? No: same route
With model sume/auto, an idempotent replay gets the same price and the same route, because resolution depends only on the request and the catalog version.

No. A replay of the same sume/auto request with the same Idempotency-Key returns the original job, and the model choice cannot flip on a retry: Sume resolves it as a pure function of the normalized request and the catalog version. The same body gets the same price and the same route.
The poll response reports "model": "sume/auto", and Sume does not disclose which family served the request.
When to pin and when to leave it on auto
Use sume/auto when you care about getting a good clip within the supported controls and do not need a named model. Pin a catalog id such as seedance-2.5 or wan-3.0 when you need a clip over 15 seconds, a specific reference-input set, or the same look across a series.
The auto create controls default to 720p and 8 seconds, with 3-10 second clips at 16:9 or 9:16. A 30-second job is a pinned-model job.
| Question | sume/auto | Pinned id |
|---|---|---|
| Who picks the family | Sume | You |
| Clip lengths | 3-10 s | Model range, up to 30 s on seedance-2.5 and wan-3.0 |
| Replay behavior | Same price and route | Same job |
| Output reveals family | No | You know it |
A replay test
Send the same request twice with one key and compare the ids. They should match, and the second call should not add a charge.
import os, requests
H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}",
"Idempotency-Key": "auto-replay-demo-001"}
body = {"model": "sume/auto", "prompt": "A vertical product clip, natural light",
"aspect_ratio": "9:16", "duration": 5}
ids = []
for _ in range(2):
r = requests.post("https://api.sume.com/v1/videos", headers=H,
json=body, timeout=30)
r.raise_for_status()
ids.append(r.json()["id"])
print(ids, ids[0] == ids[1])Do not infer the family
Sume says not to use traits of an output to guess which family ran. If the family matters to your product, pin the model id.
Sources
Related posts
More in Developers
- sume/auto is missing from GET /v1/images/models: hardcode it
Sume Image Router Auto never appears in the model list. Discovery code that only reads GET /v1/images/models will never offer sume/auto. How to handle it.
- Sume auto never names the model: what to log for TikTok AI disclosure
With sume/auto the response does not name the model family. TikTok asks if content is AI-generated, not which model made it. Log job id and date.
- sume/auto or a pinned video id after a vendor retires a model?
After the Sora removal, choose between model: sume/auto and a pinned catalog id. What each guarantees on Sume, with the 3-10 s, 720p, 8 s Auto defaults.
- sume/auto or a pinned model for 30-second video on Sume
sume/auto defaults to 8 s clips of 3 to 10 s, so a 30-second job needs a pinned id: seedance-2.5 or wan-3.0. How the two paths differ.
Written by Sume