How is a sume/auto video job billed if Auto has no price?

sume/auto is a routing name, not a model, and it has no price of its own. Sume's internal video docs state that billing keys off the resolved family, so the amount you pay is the per-second rate of the family that ran, at the provider list times the 1.25 house margin that every Video Router row carries. The submit and poll responses echo sume/auto verbatim, and the family that served the job is not disclosed.

That raises a fair budgeting question: if you cannot see the family, how do you know the price? You can, because Auto's envelope is narrow and documented.

What does an Auto clip cost in practice?

Sume's video generation docs say Auto defaults to Gemini Omni Flash 1.1, with 3 to 10 seconds, 360p to 4K, and 16:9 or 9:16. Gemini Omni Flash 1.1 bills per output second by resolution, so you can price an Auto request from its resolution and length. The table shows an 8-second clip, which is the Auto default length, at each resolution.

Where do I read the real amount?

The poll response carries usage.cost, the Sume billable amount, and the same job is readable at GET /v1/jobs/{id}/result in Sume's normal envelope. Funds are reserved at submit and the final amount is captured when the job completes, so the number to trust is the one on the finished job, not the estimate. See Jobs and results for the lifecycle.

Send an Idempotency-Key and a retry returns the original job instead of creating and billing a second one.

When should I stop using Auto for cost control?

Auto is the right default when you want a working 3 to 10 second clip with sound. It is the wrong tool when the price is the decision: Wan 3.0 at 480p is $0.0625 per second, below Gemini Omni Flash 1.1 at any resolution except 360p, and it runs longer clips. Pin the row you priced, and keep Auto for the requests where the envelope already fits.