11-second AI video API: what works past Omni's 10 s cap
Gemini Omni Flash 1.1 stops at 10 s, so an 11 s clip needs H3, H3 Max, Wan, Kling or Seedance. Which Sume ids accept 11 s and what each bills.

An 11 second clip rules out Gemini Omni Flash 1.1, whose Sume range is 3-10 s. Everything else with a longer ceiling accepts it: MiniMax H3 and H3 Max (5-15 s), Wan 3.0 (2-30 s), Kling 3 and the Seedance 2 family (4-15 s) and Seedance 2.5 (4-30 s).
Which models accept 11 seconds
MiniMax's H3 launch post says clips run up to 15 s (read 2026-10-04), and the Sume catalog lists the same 5-15 s window for both H3 ids. Wan and Seedance 2.5 go to 30 s.
| Model id | Duration range | Billed for 11 s |
|---|---|---|
| wan-3.0 | 2-30 s | 480p $0.69, 720p $1.38, 1080p $2.75 |
| minimax-h3 | 5-15 s | 480p $0.69, 768p $0.83 |
| minimax-h3-max | 5-15 s | 480p $0.69, 768p $1.10, 1080p $2.20 |
| kling-3 | 4-15 s | audio off $1.54, audio on $2.31 |
| seedance-2.5 | 4-30 s | token priced, read pricing_skus |
| seedance-2, seedance-2-fast, seedance-2-mini | 4-15 s | token priced, read pricing_skus |
| grok-imagine-video-1.5 | 4-15 s | read pricing_skus |
| higgsfield-genjutsu | 4-30 s (source length) | read pricing_skus |
| h3-max-recast | 5-30 s (source length) | 768p $4.13, 1080p $6.19 |
Auto and pinned ids over 10 seconds
The Auto router's create controls default to 3-10 s clips at 16:9 or 9:16, so an 11 s job is the point where you should pin a model rather than rely on Auto. The stored post on Auto versus a pinned model past 10 s walks through that choice.
Google's Omni page documents extension in 10 s steps up to 40 s total (read 2026-10-04, Omni docs), but that is a Google feature. Sume's catalog entry for Omni is a single 3-10 s generation.
What a 11 second request costs
Sume bills the provider list price times 1.25, rounded up to the next cent. The amount is reserved when you submit and refunded if the job fails, so a rejected or failed clip does not cost you. The /v1/videos/models descriptor lists the billable rate in pricing_skus, which is the field to trust over any number in a blog post.
Eleven seconds at the H3 768p rate bills $0.83; Wan at 720p bills $1.38; H3 Max at 1080p bills $2.20.
Check 11 seconds against the live catalog
Duration support lives in the catalog, not in this page. Each entry on GET /v1/videos/models carries supported_durations, which is every whole second from the model minimum to its maximum, so one membership test answers the question. This script lists every model that accepts 11 s, with its resolutions and billable rates.
Set SUME_API_KEY first. See the Video Generation docs for the request and polling lifecycle.
import os
import requests
N = 11
resp = requests.get(
"https://api.sume.com/v1/videos/models",
headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"},
timeout=30,
)
resp.raise_for_status()
for m in resp.json()["data"]:
if N in m["supported_durations"]:
print(m["id"], m["supported_resolutions"], m["pricing_skus"])Sources
Related posts
More in Models
- 13-second AI video API: MiniMax H3 at 768p and other Sume ids
Thirteen seconds fits MiniMax H3 and H3 Max (5-15 s), Wan 3.0, Kling 3 and Seedance. Billed price per resolution for a 13 s clip on Sume.
- 14-second AI video API: one Sume request or stitched extensions
Fourteen seconds is one request on Sume with H3, Wan, Kling or Seedance. Veo reaches that length only by extension. Prices for a 14 s clip inside.
- 17-second AI video API: only Wan and Seedance 2.5 clear 15 s
Seventeen seconds is past the 15 s wall of H3, Kling and Seedance 2. Wan 3.0 and Seedance 2.5 accept it; Wan bills 17 s at 480p to 1080p below.
- 18-second AI video API: draft at Wan 480p, then render final
An 18 s Wan 3.0 clip bills three different amounts on Sume, one per resolution. Draft at 480p, check the cut, then pay for 720p or 1080p once.
Written by Sume