routing_preset kling or grok on Video 1.0: accepted, then ignored

Setting routing_preset to grok or kling on Video 1.0 does not pick that family: the docs call the field deprecated and ignored, and every value uses Auto. To choose a family, call POST /v1/videos with a catalog model id.

Which routing_preset values are ignored?

The docs list cost, speed, quality, grok and kling. Retired values are accepted and ignored, so an old integration that sends one keeps working but gets Auto selection.

What does the request see instead?

Auto selection, capability validation and pricing apply to the legacy URLs, and receipts report sume/auto. The docs add that you should not infer the served family from the output.

How do I pin a family?

Send a catalog id to /v1/videos. Video 1.0 has no model body field, so pinning means moving routes.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: pin-001" \
  -d '{"model":"seedance-2.5","prompt":"A slow push-in on a ceramic mug","resolution":"720p","duration":8,"aspect_ratio":"16:9"}'

Should I keep Auto instead?

Use sume/auto on /v1/videos when you do not need a specific family; see Sume Auto or pinned. Read the Video 1.0 docs for the deprecation wording.

What does a job on Auto cost?

Billing is reserved on submit at provider list times 1.25, and the poll response reports usage.cost as the Sume billable amount. Sending an Idempotency-Key makes retries safe, because a replay returns the original job.

Video 1.0 uses the same Auto pricing as sume/auto on /v1/videos, so removing routing_preset changes nothing about the charge.