Does a reference video change Seedance 2.0's price?

Yes. On Sume, attaching a reference video to seedance-2 adds 15 assumed input seconds to the billable tokens and multiplies the total by 0.6. For a 10-second 720p 16:9 clip that reserves $5.67 with a reference video against $3.78 without one, before the 5.5% agent fee.

The reserve is computed from the provider list price in Sume's pricing code, then multiplied by 1.25. fal's reference-to-video page, read 2026-09-29, states the same 0.6× rule for video input. See the Video generation docs for the request shape.

How is a reference-video clip priced?

The token count uses the output length plus the input video's length, and the 0.6× multiplier applies to the whole amount. Sume does not measure your file: it assumes 15 seconds of input for any reference video.

What does fal state about video input?

fal's page says the token formula includes both input and output duration, and it lists a 0.6× discount when there is video input. Its per-second examples are quoted in fal's own units for its own endpoints; they are not Sume prices.

Do image or audio references change the price?

Not in Sume's Seedance estimate. The price code looks for a reference video and reads no image or audio references, so a request with nine images and no video reserves the same as a request with none. The estimate depends on resolution, aspect ratio, duration and the presence of a reference video, and on the model id's rate.

What if my reference clip is shorter than 15 seconds?

The reserve still uses the assumed 15 seconds; the code does not read your file's length at submit. The docs do not describe a later adjustment of that assumption, so check usage.cost on the finished job and keep the clip within the vendor's limits. fal lists up to 3 reference videos with a combined 2 to 15 seconds.

How do I attach a reference video?

Add a video_url entry to input_references with a public HTTPS URL. The Seedance 2.x ids accept image, video and audio reference types.

curl -X POST https://api.sume.com/v1/videos \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "seedance-2",
    "prompt": "Recreate the camera move from the reference with a glass bottle on a marble counter",
    "duration": 10,
    "resolution": "720p",
    "aspect_ratio": "16:9",
    "input_references": [
      {"type": "video_url", "video_url": {"url": "https://example.com/reference.mp4"}}
    ]
  }'

How do I see what I was actually charged?

The reserve is taken at submit. The finished job's usage.cost is the Sume billable amount, so read it there and reconcile it with your own logs rather than with a table. If you run many reference-video jobs, log the reserve and usage.cost side by side for a week before you set a budget.