Magnific video upscaler per-frame price vs Sume per-second

Runway bills the Magnific video upscaler per output frame, so the cost grows with frame rate as well as length. Sume's video upscale is priced per input second instead: the rate is $0.009 per video second, an omitted duration_seconds reserves 5 seconds, and the maximum is 30 seconds.

Vendor numbers are from Runway's pricing page, read 2026-09-30. Sume numbers come from the rate card and the API contract.

How does Runway bill the Magnific video upscaler?

The page says it is billed per output frame, not per second of video. Credits are ceil(USD / 0.01), where USD is the per-frame rate times fps times duration_seconds, with a 1 credit minimum. When fpsBoost is on, the output frame count may differ from the input and change the cost.

How does Sume price a video upscale?

The rate-card row is "Video upscale". The contract describes it as priced per input second after Sume margin. Because the unit is the input second, frame rate does not enter the price. A 10 second clip is 10 input seconds whether it is 24 or 60 fps, while the frame-billed version of the same clip is 240 frames at 24 fps and 600 at 60 fps.

What are the default reserve and the cap?

If you omit duration_seconds, Sume reserves 5 seconds. The maximum is 30 seconds, so a longer source has to be trimmed or split first. Paid generation reserves the estimated amount at submit and captures it on success; failed jobs release or refund the reservation where applicable (see Jobs and results).

How do I convert one unit to the other?

Convert to one unit. For Runway, multiply the per-frame rate by fps and seconds (300 frames for 10 seconds at 30 fps). For Sume, multiply the rate-card price by the input seconds you will pass. Set duration_seconds explicitly so the reserve matches your clip. From an agent, the MCP tool is video_upscale_create; see MCP tools and gates. The general API flow is in AI video upscale API.