Luma credits in dollars: Seedance 2.0 1080p 5s on each plan vs Sume

On Luma's monthly plans a credit costs 0.3 cents (Plus), 0.225 cents (Pro) or 0.2 cents (Ultra). Luma lists Seedance 2.0 text-to-video at 1080p as 126 credits a second, so a 5-second clip is 630 credits: $1.89 on Plus, $1.42 on Pro and $1.26 on Ultra. The same clip priced through Sume's Seedance 2 row is about $4.25. The gap is real, and it comes from how each side charges, not from a different model.

What does one Luma credit cost on each plan?

Luma's pricing page lists three individual plans. Dividing the monthly price by the credits included gives the price of one credit. The page also shows annual billing, which lowers the per-credit price further.

What does a 5-second 1080p clip cost in dollars?

Luma's sample costs give credits per second or per clip; multiply by clip length and the plan's per-credit price. Luma lists Kling Omni as a range, so the table keeps the range instead of picking an end.

How does Sume price the same Seedance 2.0 clip?

Sume does not sell a credit bundle for video. The Video Router docs say Sume bills the provider list rate times 1.25 on each model, and the job returns the usual async envelope. For Seedance 2 at 1080p, 16:9, 5 seconds, Sume's own estimator in the pricing package gives $4.2525 (about $4.25). At 720p the same clip is $1.89, and the faster Seedance 2 Fast row is $3.40 at 1080p.

That estimate is the pre-run reserve; the job receipt carries the final charge. Treat it as the number to budget against.

Why is the Luma plan rate lower, and when does Sume still make sense?

A Luma credit price is only that low if you use the credits. A plan is a prepaid monthly allotment, so a month you do not fill is a month the effective price per clip goes up. Sume bills per job from a wallet, with plan tiers that change concurrency and access, not the per-second rate.

So the honest summary: if you will reliably burn a Luma plan's credits on Seedance 2.0, the plan rate is cheaper per clip. Sume is the better fit when volume is lumpy, when you want one API key and one balance across many models, or when you need a model Luma does not list. I did not find Luma's own Ray3.2 in Sume's Video Router docs, so there is no Sume figure to set beside that row.