Alibaba's Sora 2, Veo 3.1, Kling 3.0 migration table vs Sume ids
Alibaba Model Studio maps Sora 2, Veo 3.1 and Kling 3.0 to happyhorse-1.1 models. Which of its targets are Sume catalog ids, and how model: sume/auto fits in.
Alibaba's Model Studio page maps closed-source Sora 2, Veo 3.1 and Kling 3.0 text-to-video and image-to-video use to happyhorse-1.1-t2v and happyhorse-1.1-i2v. Of the models on that page, only Wan 3.0 has a Sume catalog id (wan-3.0); no HappyHorse id appears in the Sume video catalog list.
Mapping is from the Alibaba page, read 2026-10-01. Sume ids are from Video Router.
What does Alibaba's migration table say?
Alibaba's recommendation depends on the task. Its Wan 3.0 entries are listed separately as general recommended models with their own use cases.
| Task | Alibaba model id | Resolution and length |
|---|---|---|
| Text-to-video (replacing Sora 2, Veo 3.1, Kling 3.0) | happyhorse-1.1-t2v | 480P-1080P, 3-15 s |
| First-frame image-to-video | happyhorse-1.1-i2v | 480P-1080P, 3-15 s |
| Video editing | happyhorse-1.0-video-edit | 720P, 1080P, 3-15 s |
| T2V, first/last frame, reference | wan3.0-video | 480P-1080P, 2-30 s |
Which of these ids exist on Sume?
The Sume catalog lists seedance-2.5, seedance-2-mini, seedance-2, seedance-2-fast, kling-3, wan-3.0 and several others. wan-3.0 accepts 2 to 30 seconds at 480p, 720p and 1080p, which matches the range Alibaba lists for wan3.0-video. The Alibaba id spelling differs (wan3.0-video against wan-3.0), so use the Sume spelling in requests. Sume lists kling-3 directly, so a Kling 3.0 workload does not need a substitute there.
For how Wan 3.0 is exposed on another platform, see Wan 3.0 on Runway vs the Sume id.
How do I avoid pinning a model at all?
Send model: "sume/auto" on POST /v1/videos and Sume picks the model. When you need an explicit pass-through id, use Video Router and pick from the catalog; read the capabilities of each row instead of assuming one envelope.
What should I check before migrating?
Compare length first: HappyHorse is listed at 3 to 15 seconds, while wan-3.0 and seedance-2.5 reach 30. Then check resolution, aspect ratio and audio on the catalog row. A model that is not in the Sume catalog cannot be requested through Sume, whatever the vendor table recommends.
Sources
Related posts
More in Developers
- Nova Reel start_async_invoke S3 output vs a Sume result URL
Nova Reel's start_async_invoke writes output.mp4 to your S3 bucket and needs IAM. A Sume job returns a result_url and durable media.sume.com links.
- ant apply agent file: declare the Sume server, keep the key out
In an ant apply agent file, declare the Sume server by name and URL, https://mcp.sume.com/mcp. The API key belongs in a vault, never in the committed file.
- Argil audio upload 50 MB vs Sume Fabric's 10 MB audio URL
Argil takes mp3, wav and m4a uploads up to 50 MB. Sume's Fabric route takes a Sume-hosted audio URL up to 10 MB; H3 Max lip sync wants 5-14.8 seconds.
- AssemblyAI Sync API: one call, and Sume STT sync mode
AssemblyAI's Sync API returns a short-clip transcript in one POST. Sume STT mode sync waits up to 30 seconds, then returns the job id to poll if not done.
Written by Sume