FLUX video upscale 1.5x to 3x: limits, and Sume's upscaler

BFL's FLUX Video Upscale scales a clip 1.5x to 3x, takes clips up to 20 seconds and 50MB, and outputs up to 2560x1440. Sume does not list it; Sume has its own video upscale endpoint, POST /v1/video-upscale-1.0/upscale, which takes a public HTTPS video_url and a duration_seconds value of up to 30.

BFL's figures are from its 2026-08-20 release note. Sume's come from its API schema and MCP tool list, read 2026-09-29.

What are FLUX Video Upscale's limits?

BFL lists two creativity modes, a precise one at $0.07 and a creative one at $0.10, both per megapixel-second. The endpoint is POST /v1/flux-tools/video-upscale-v1.

What does Sume's video upscale take?

The request needs a public HTTPS video_url. scale_ratio defaults to 2 and enhancement_tier is fast (default), standard or pro. duration_seconds sets the reservation: omit it to reserve 5 seconds, and the maximum is 30. The job is priced per input second after Sume margin.

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

Why do the prices not line up?

BFL bills per megapixel-second, so cost grows with resolution as well as length. Sume's description says per input second, so length alone drives the estimate. To compare, price one real clip on both, not the headline rates.

Can an agent call it?

Yes, hosted MCP lists video_upscale_create among the paid tools, which need an idempotency_key.

How do I run Sume's upscale as a job?

The route is asynchronous like other generation. The request has a mode field: async is the default and returns polling URLs at once, webhook stores a callback for the terminal result, and sync or subscribe block for up to wait_timeout_seconds, at most 30. Video work routinely outlasts that wait, so poll the status URL or use a webhook for a real clip.

Paid job creation accepts an Idempotency-Key header so a retry does not create a second job.

Which limits should I check before I choose?

Check clip length, file size, target size and price basis on both sides. BFL lists 20 seconds, 50MB and 2560x1440. On Sume the length figure is the duration_seconds reservation of up to 30, and the published schema I read gives no file-size or output-size limit, so test with your real file before you commit a batch.

How do I compare the results?

Upscale the same short clip on both services and view them side by side at the size you will publish. Judge sharpness, flicker between frames and any change to faces or text, and note what each cost you. BFL offers two creativity modes and Sume offers three enhancement tiers, so compare the closest settings first and only then try the others. Keep your source file so you can rerun the test later.