Wan 3.0 has six regional endpoints; Sume has one base URL

Alibaba serves the Wan 3.0 API from six regions, Singapore, Beijing, US (Virginia), Tokyo, Frankfurt and Hong Kong, and each regional URL needs a workspace id substituted in. On Sume you call one base URL, https://api.sume.com/v1/videos, with a bare model id like wan-3.0, and the request has no region or Alibaba workspace field.

Alibaba's list comes from its Wan3.0 Video Generation API Reference, read on 2026-10-02. Sume's side comes from Video generation and Sume basics.

What does the regional setup look like on Alibaba?

The page lists six regions, each with its own base URL and a {WorkspaceId} placeholder. Beyond the URL, the call pattern is asynchronous only: you send an async header, create a task, then poll the task id, which stays valid for 24 hours. There are two model names, wan3.0-video for the standard version and wan3.0-video-prime for the high-speed one.

For a team that is new to Alibaba Cloud, the work is picking a region that matches where your account and data live, creating the workspace, and keeping keys for that region together. A key from one region is not something I can assume works in another, because the page does not say it does.

What does the Sume side look like?

Sume API keys resolve to a workspace, and the basics page says not to send workspace_id in request bodies. Model ids are bare catalog ids; the docs state Sume's published contract never carries a provider-org prefix. The catalog at GET /v1/videos/models lists what each id supports, and wan-3.0 accepts 2 to 30 seconds.

What the pages I read do not tell you is where Sume runs the underlying Wan job. There is no region parameter, so you cannot choose one, and I will not guess at where it executes. If data residency decides your purchase, ask Sume before committing; do not infer it from this post.

Does the single URL change my code?

It removes code: no regional URL table, no workspace id substitution, one key. It also removes control, because the Alibaba-only switches are not reachable. Sume's docs say provider.options is rejected with 400 unsupported_parameter in v1 and seed and size are rejected for every model. The prime model name is not a separate id either; the post on Wan 3.0 Prime covers that gap.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: wan-region-001" \
  -d '{"model": "wan-3.0", "prompt": "A tram at dawn, slow dolly", "duration": 6, "resolution": "720p"}'

Which should I choose?

For the price math on the Sume side, see Wan 3.0 pricing.

• Choose Alibaba direct if you need a specific region, the prime model name, or provider-side switches such as prompt rewriting and watermark.
• Choose Sume if you want one key and one job vocabulary across Wan, MiniMax H3 and others, with usage billed as provider list times 1.25.
• Either way, store the job or task id the moment you get it.