Alibaba Wan 3.0 on OpenRouter vs Sume: id, seed and aspect ratios

Wan 3.0 is reachable on both OpenRouter and Sume with the same duration range, 2 to 30 seconds, but the request differs in three ways: the model id is alibaba/wan-3.0 on OpenRouter and wan-3.0 on Sume, OpenRouter accepts seed where Sume rejects it, and billing is from OpenRouter's own balance there against a workspace USD balance at provider list times 1.25 here. The core fields (prompt, duration, resolution, aspect_ratio) carry over.

Read on 2026-10-01: OpenRouter's alibaba/wan-3.0 page, Alibaba Cloud's Wan3.0 announcement, and Sume's Video Generation docs.

What does each side list?

OpenRouter's page lists 480p, 720p and 1080p, aspect ratios 16:9, 4:3, 1:1, 3:4 and 9:16, and seed support with the note that determinism is not guaranteed for every provider. Sume's docs list the 2 to 30 second range for wan-3.0 and say no v1 model accepts seed. I did not find an aspect-ratio or resolution list for wan-3.0 in Sume's prose, so read it from GET /v1/videos/models.

What breaks when you move a request?

Three edits: change the base path (https://api.sume.com/v1/videos, no /api segment), replace alibaba/wan-3.0 with wan-3.0, and delete seed. Sume's catalog reports seed: false for its video models, so drop the field; check the live catalog row for wan-3.0. Add an Idempotency-Key header on Sume if you want safe retries.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: wan-move-001" \
  -d '{"model": "wan-3.0", "prompt": "A tram crosses a rainy bridge at dusk", "duration": 10, "resolution": "720p"}'

Which should you pick?

If you rely on seed to reproduce a shot, OpenRouter is the one of the two that accepts it, and even there OpenRouter says determinism is not guaranteed for every provider. If you want one key and one balance across many video models, with an idempotency header and a job also readable at GET /v1/jobs/{id}/status, that is the Sume side.

Whichever you choose, pin the model id in your logs. Sume's sume/auto echoes itself and never names the family that ran, so a Wan shot made through auto cannot be traced to Wan afterwards. If a clip must be Wan, send wan-3.0.

Prompts transfer as they are; check optional fields such as frame_images and input_references against each side's docs before moving them.

Limits

Alibaba's announcement lists $0.05, $0.10 and $0.20 per second at 480p, 720p and 1080p before promotions; neither OpenRouter's page nor Sume's docs tell me what each platform charges, so compare usage.cost on a short test rather than assuming parity.