Upscale twenty 12-second clips for $2.16 with Sume video upscale

Sume Video Upscale 1.0 is priced at $0.009 per input second, with a 30-second maximum per video. Twenty clips of 12 seconds each are 240 input seconds, and 240 x $0.009 = $2.16.

Cost by clip length

Rates from the public catalog, read 2026-10-09.

Tell it the duration

If you omit duration_seconds, Sume reserves 5 seconds. For a 12-second clip, send duration_seconds: 12 so the reserve matches the clip. The field accepts 1 to 30.

curl -X POST https://api.sume.com/v1/video-upscale-1.0/upscale \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: vup-012" \
  -d '{"video_url":"https://example.com/clip-012.mp4","upscale_factor":2,"duration_seconds":12,"enhancement_tier":"standard"}'

Body fields

• video_url: public HTTPS URL.
• upscale_factor or scale_ratio: 1.1 to 4.
• enhancement_tier: fast, standard or pro. The catalog lists one per-second rate; it does not state a different price for each tier.
• model and provider endpoint keys are rejected.

Longer than 30 seconds

A 45-second clip exceeds the cap. Cut it into two parts with video trim at $0.02 each, then upscale each: 2 x $0.02 + 45 x $0.009 = $0.445. The trim route is cheaper than any alternative that re-generates the clip.

Planning a batch

Cost is linear in input seconds, so 100 clips of 12 s is 1,200 s x $0.009 = $10.80. If a source is only 8 seconds and you omit duration_seconds, the reserve is 5 seconds, which is lower than the clip; give the real value. Check one result per tier before running the batch, since the catalog does not publish a quality difference between fast, standard and pro. Every media job follows the same lifecycle: submit with an Idempotency-Key, receive a job, poll GET /v1/jobs/:id/status until it is ready, then read GET /v1/jobs/:id/result. A retry with the same key does not queue a second job, so a network error during submit never doubles a charge.