Runway Model Router allow and deny lists vs Sume auto

Runway's Model Router lets you configure model allow and deny lists and optional per-modality credit ceilings. Sume has no allow or deny list. You either pin one catalog model by id, or send model: "sume/auto" and let Sume pick, with the family that ran never disclosed.

Runway's statement is from its July 23rd, 2026 changelog entry; Sume's from the Video Router docs and video generation guide, read 2026-10-01.

What does Runway's router offer?

The entry says you create a saved routing configuration once, reference it by configId, and the router filters to eligible models and selects one by your optimization preference (cost, latency or quality). Allow and deny lists, per-modality credit ceilings for video, image and audio, and a dryRun preview are part of that configuration.

How do I control the model on Sume?

There are two documented choices, and nothing in between.

What happens to an id that is not in the catalog?

Ids not listed in GET /v1/video-router/models are rejected on generate. Models can also be retired from automatic picking: seedance-2 and seedance-2-mini are no longer chosen by any default, but stay routable when you name them.

What should I do?

If you need a deny list, keep your allowed ids in your application and pass the one you want. If you use sume/auto, the poll response reports sume/auto and you should not infer the family from the output. For how Runway bills the selected model, see Runway Model Router billing.