Video upscale hold: omit duration_seconds and Sume reserves 5 s

Sume video upscale reserves from duration_seconds, or 5 seconds when you omit it. Hold table for 5, 15 and 30 seconds at $0.009 per second and the 402 case.

3 min readSume
All posts

Always send duration_seconds on a Sume video upscale. The catalog states the price is per input second ($0.009), that omitting duration_seconds reserves 5 seconds, and that the maximum is 30 seconds. A 30-second clip sent without the field is held as 5 seconds ($0.045), not $0.27.

Hold by duration

Computed from the published per-second rate
`duration_seconds`Hold at $0.009/s
omitted$0.045
5$0.045
15$0.135
30$0.27

Why it matters

Reservations are made at submit and a shortfall returns 402 insufficient_credits (Errors and credits). Declaring the real length keeps the hold honest and the balance check meaningful for the whole clip.

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: up-30s-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/clip.mp4",
    "upscale_factor": 2,
    "duration_seconds": 30
  }'

Constraints

  • upscale_factor (alias scale_ratio) is 1.1 to 4.
  • enhancement_tier is fast, standard or pro.
  • Do not send model or provider endpoint fields; the route refuses them.
  • Longer than 30 s: cut with video-trim first.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume