Veo 3.1 Lite: 10 seconds at 720p costs $0.50; Wan 3.0 on Sume $1.25

A 10-second 720p clip on Veo 3.1 Lite costs $0.50 on Google's Gemini API (10 x $0.05 per second). The nearest cheap 720p row Sume lists is Wan 3.0 at $1.25 (10 x $0.125). Sume does not list Veo in its video catalog, so the two cannot be called from one Sume key; this post is a price check for someone deciding whether to build on Google directly or on Sume's wan-3.0 row.

Google's page names Veo 3.1 Lite as veo-3.1-lite-generate-preview and quotes its price as a video-with-audio price. Sume's docs say wan-3.0 accepts 2 to 30 seconds and that Sume bills the provider list price times 1.25.

The numbers side by side

Google quotes per second of output in USD. Sume's figures are the shared list prices at default options, already including the 1.25 multiplier.

What the gap means

At 720p the Google row is $0.75 cheaper per 10-second clip, a ratio of 2.5 to 1. At 1080p the gap is $1.70 (3.12 to 1). Over 100 clips of 10 seconds at 720p that is $50.00 against $125.00.

Price is one input. Veo 3.1 Lite does not output 4K per Google's page, and your workflow may need first and last frame control, reference images, or one API that also handles TTS, music and timeline renders. Those are the cases where staying inside Sume's catalog can be worth a higher per-second rate.

Checklist for a draft pipeline

If the choice is close, run the same ten prompts through both and compare the rejects, not only the price. A cheap clip you discard half the time costs more than the sticker suggests.

• Cost per kept clip = price per clip divided by the share you keep. At $0.50 and a 50% keep rate that is $1.00; at $1.25 and an 80% keep rate it is about $1.56.
• Check the duration range: Wan 3.0 on Sume accepts 2 to 30 seconds, so a 30-second pass is 30 x $0.125 = $3.75 at 720p.
• Check what your output needs: Sume's Wan row lists 480p, 720p and 1080p, with 1080p at $0.25 per second.
• Keep Idempotency-Key on retries if you use Video Router, so a replay gets the same price and route.

Calling the Sume row

Sume's /v1/videos endpoint is OpenRouter-compatible and asynchronous: you submit, receive a polling_url, and poll until the status is completed. A 10-second 720p Wan 3.0 request looks like this.

curl -X POST "https://api.sume.com/v1/videos" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"wan-3.0","prompt":"A paper boat crossing a puddle, overhead shot","resolution":"720p","duration":10}'

Before you decide

Call GET /v1/videos/models to read the live durations and resolutions, because limits differ per model. Prices on both sides can change; the tables above carry the date they were read. If your clips are mostly drafts, the Veo Lite figure is hard to beat on price alone, and if they need to live next to the rest of a Sume pipeline, the Wan row is the one to test.