Runway Seedance 2 Mini 64-credit minimum vs Sume's mini reserve
Runway bills seedance2_mini at 16 credits per second with a 64-credit minimum. Sume's seedance-2-mini reserves list x 1.25 by the second; 4, 5 and 10 s costs.

Runway's API pricing page lists seedance2_mini at 16 credits per second at 480p or 720p, with a 64-credit minimum. At $0.01 per credit that is $0.16 per second and a $0.64 floor, which is exactly 4 seconds. Sume's seedance-2-mini reserves the provider list price times 1.25 by the second: $0.36 for 4 seconds at 480p and $0.76 at 720p, before the agent fee.
Runway facts are from its pricing page, read 2026-10-01, including its statement that credits are $0.01 each. Sume's rule is from the video docs; the figures are computed from its pricing code.
What does the 64-credit minimum change?
Nothing at 4 seconds or longer, since 4 x 16 = 64. Mini clips run 4 to 15 seconds on Sume, so the floor and the per-second charge meet at the shortest clip. The page lists the same 16 credits per second for 480p and 720p.
What does Sume reserve for the same clips?
Sume prices resolution separately. The estimates below are for 16:9 clips, computed from the same code the API uses to reserve at submit. Add the 5.5% agent fee that applies by default.
| Clip | Runway (16 credits/s, 64 min) | Sume 480p | Sume 720p |
|---|---|---|---|
| 4 seconds | $0.64 | $0.36 | $0.76 |
| 5 seconds | $0.80 | $0.44 | $0.95 |
| 10 seconds | $1.60 | $0.88 | $1.89 |
| 15 seconds | $2.40 | $1.32 | $2.84 |
Which resolutions does each side offer?
Runway's line covers 480p and 720p. Sume's docs name 1080p for seedance-2 and do not mention it for mini, so treat mini as 480p and 720p and read GET /v1/catalog before sending anything else.
How do I avoid overspending while testing?
Draft at 480p, then render the keeper. See Seedance 2.0 Fast vs Mini for how the ids differ, and cheapest Seedance 2.0 API for the price ladder. If a balance cannot cover the estimate, the request fails with 402 insufficient_credits rather than a partial run.
Sources
Related posts
More in Pricing
- Runway Veo 3.1 audio is 40 credits a second, 20 without; Sume's toggle
Runway bills Veo 3.1 at 40 credits per second with audio and 20 without. On Sume, kling-3 has a generate_audio toggle with two list rates.
- Runway wan3 at 5, 10 and 20 credits a second vs Sume Wan 3.0
Runway lists wan3 at 5, 10 and 20 credits per second for 480p, 720p and 1080p. Sume's wan-3.0 bills list x 1.25; here are both for 5 and 10 seconds.
- Shared credits per seat vs one Sume workspace balance and keys
Runway Team adds 6,900 credits per seat to a shared pool. Sume uses one workspace USD balance and workspace-scoped API keys; concurrency follows the plan.
- Shotstack $0.30 per minute vs Sume's $0.10 Timeline render rate
Shotstack pay-as-you-go renders cost $0.30 per minute, billed by the second. Sume's Timeline is $0.10 per output minute, rounded up. Costs for three lengths.
Written by Sume