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.

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
| `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(aliasscale_ratio) is 1.1 to 4.enhancement_tierisfast,standardorpro.- Do not send
modelor provider endpoint fields; the route refuses them. - Longer than 30 s: cut with video-trim first.
Sources
Related posts
More in Developers
- Wan 3.0 draft and final need different Idempotency-Keys (409)
Reusing one Idempotency-Key for a 480p draft and a 1080p final of the same prompt returns 409 idempotency_conflict. A Python key builder that avoids it.
- Webhook signature mismatch: Sume fingerprint vs OpenRouter t=,v1=
A video webhook that fails verification has three usual causes: parsed body, wrong secret, wrong header format. Sume adds a secret fingerprint header.
- Test a video webhook receiver before the first job: Sume vs fal
Sume sends a signed dummy webhook.test with one API call. fal retries real results up to 31 times and treats 3xx as failure, so test your URL first.
- Which languages? Sume's language fields vs MAI's 23 and 60 counts
Microsoft states 23 languages for MAI-Voice-2.1 and 60 for MAI-Transcribe-2-Streaming. Sume publishes no count; here are its language fields.
Written by Sume