Wan 3.0 file_url, web_url, enable_thinking: not in Sume v1

If you are porting a Wan 3.0 call and it carries file_url, web_url or enable_thinking, drop them. The Sume catalog states that wan-3.0 does not expose those fields in v1, and the provider.options object must stay empty, so there is no passthrough route for them either.

What you can send instead is the normal Sume request: prompt, duration (2 to 30 seconds), resolution, aspect_ratio, frame_images for first and last frame, and input_references for images, video and audio.

What replaces each field

The mapping is not one to one, so decide per field whether you need the behavior at all.

Why Sume rejects instead of ignoring

The video API fails closed on anything it cannot honor. A silently ignored field would leave you billed for a clip that did not do what you asked, so the API returns an error and you fix the request. That is the same rule that rejects size and seed on this surface.

A minimal Wan request

This is a request that uses only fields the catalog accepts. Replace the URL with a public HTTPS image you control.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "wan-3.0",
    "prompt": "A slow push-in on the product, soft daylight",
    "duration": 8,
    "resolution": "720p",
    "aspect_ratio": "16:9",
    "input_references": [
      {"type": "image_url", "image_url": {"url": "https://example.com/product.png"}}
    ]
  }'

When the missing field matters: checklist

If your workflow depends on a web-grounded or reasoning mode, Sume's wan-3.0 is the wrong tool for that step. Do the research or planning in an agent turn, then hand the result to the video call as plain prompt text. Read the live catalog row to see whether a later release adds any of these fields.

Work through the request body once before you send the first job. Each line below removes a way for the call to fail.

Treat the catalog row as the contract. Provider documentation may describe more fields than the Sume row exposes, and only the row tells you what your request can include today. When it changes, your validator should pick the change up from the row, not from a code edit.

• Strip every field that is not in the catalog row, then diff your body against GET /v1/video-router/models/wan-3.0.
• Move media to input_references with public HTTPS URLs.
• Keep duration between 2 and 30 and resolution to 480p, 720p or 1080p.
• Send an Idempotency-Key so a retry replays the job and does not start a second one.