OpenRouter video provider.options on Sume: rejected, not dropped

A non-empty provider.options on POST /v1/videos returns 400 unsupported_parameter on Sume, because v1 runs a single backend per model and every model's allowed_passthrough_parameters is empty. Remove it when you port a client.

What is provider.options?

OpenRouter's page describes provider as provider-specific passthrough configuration. Sume keeps the field but the docs say options are keyed by provider slug and only the matched provider's are forwarded.

What does v1 do?

The catalog field decides what may pass through, and today it lists nothing.

What does a valid body look like?

The docs example sends an empty options object.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: prov-001" \
  -d '{"model":"seedance-2","prompt":"A time-lapse of a flower blooming","provider":{"options":{}}}'

How do I tune output then?

Use the documented fields: resolution, aspect_ratio, duration and references. See the video docs.

What other differences should I check?

The differences table also covers size, seed, the webhook envelope, model ids and billing. Zero Data Retention is another delta: OpenRouter's page says video generation is ineligible for it, and Sume has no ZDR toggle.

Billing is a workspace USD balance reserved on submit at provider list times 1.25.