Veo 3.1 price per second vs Sume's Video Router models

Google lists Veo 3.1 at $0.05 to $0.60 per second. Sume does not offer Veo 3.1 in its v1 catalog; here is the 8-second, 100-clip math for what it does.

4 min readSume
All posts

Google's Gemini API page lists Veo 3.1 at $0.05 to $0.60 per second depending on resolution (read 2026-10-07), so an 8-second clip is $0.40 to $4.80 and 100 clips are $40 to $480. Sume does not offer Veo 3.1: its docs list Veo 3.1 as not in the v1 catalog. If you need Veo, buy it from Google.

Veo 3.1 at Google's list

The multiplication is simple. $0.05 x 8 s = $0.40 per clip, and $0.60 x 8 s = $4.80. For 100 clips that is $40.00 and $480.00. I did not read which resolution maps to which price on the page summary, so treat the two ends as a range.

Runway's API page also lists Veo 3.1 at 10 to 40 credits per second at $0.01 per credit (read 2026-10-07), or $0.10 to $0.40 per second, so a reseller price differs from Google's own range.

What Sume offers in the same clip size

These are Video Router rows from the Sume docs, priced at provider list x 1.25 for an 8-second clip. They are different models with different looks, so the table is a cost reference, not a quality ranking.

8-second clip, 100-clip batch (Google page read 2026-10-07; Sume rows from Sume docs list x 1.25)
OptionPer second8 s clip100 clips
Google Veo 3.1, low end$0.05$0.40$40.00
Google Veo 3.1, high end$0.60$4.80$480.00
Sume Wan 3.0, 480p$0.0625$0.50$50.00
Sume Wan 3.0, 720p$0.125$1.00$100.00
Sume H3 Max, 768p$0.10$0.80$80.00
Sume Gemini Omni Flash 1.1, 720p$0.125$1.00$100.00
Sume Gemini Omni Flash 1.1, 4K$0.375$3.00$300.00

The honest read

Sume costs more than the list price for the same underlying model, because of the 25 percent margin. Where you want one API for several video models, a job queue and a single balance, that is the trade. Where you specifically want Veo, go direct; there is no Sume workaround to claim here.

Sume's own docs also say the Video Router catalog changes. Call GET /v1/video-router/models for the current set before you plan a launch around a model name.

A decision rule

If the model is fixed by creative requirements (you need Veo 3.1 specifically), the price question is moot, because Sume cannot sell it to you. If the requirement is looser (a photoreal 8-second clip with native audio), then the question becomes the cost per usable clip, not per second.

A simple test: generate 10 clips on each candidate, count how many you would publish, and divide the batch cost by that count. A $0.50 clip with a 40 percent keep rate costs $1.25 per kept clip; a $1.00 clip with an 80 percent keep rate costs $1.25 as well. Per-second prices tell you nothing until you know the keep rate, so measure it on your own prompts before you scale to 100.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume