Kling V3 Pro vs Standard vs O3 per minute
Hedra's Artificial Analysis table puts Kling V3 Pro at $20.16 per minute and V3 Standard at $15.12. How to compare per-minute prices with Sume per-second SKUs.

On Hedra's Artificial Analysis table, Kling V3 1080p Pro is listed at $20.16 per minute, Kling V3 720p Standard at $15.12 and Kling O3 Omni Pro at $16.80. Those are per-minute vendor-side figures; to compare them with Sume you convert to per-second and read the price from the Sume catalog, not from a blog.
The figures as published
The numbers below are copied from the Hedra page, which cites Artificial Analysis. The same page lists Kling V3 Pro text-to-video at an Elo of 1,110, ranked sixth. Treat the table as a snapshot of that page on the read date, not as a live price.
| Model and tier | Price per minute |
|---|---|
| Kling V3 1080p Pro | $20.16 |
| Kling V3 720p Standard | $15.12 |
| Kling O3 Omni Pro | $16.80 |
Convert before comparing
A per-minute price hides how you actually buy: clips are seconds long. Divide by 60 to get the per-second rate, then multiply by the clip length you intend to ship. A 10-second clip at the V3 Pro figure is one sixth of the per-minute price. The same arithmetic applies to any other vendor's table, so the comparison stays fair only if resolution and audio are the same on both sides.
Also check what the per-minute figure includes. Vendor tables often price a specific resolution tier, and a cheaper tier can mean a different output size, not just a different quality.
- Per-second rate = per-minute price / 60.
- Clip cost = per-second rate x seconds shipped.
- Match resolution, audio and aspect ratio before ranking.
Where Sume fits
Sume does not publish a per-minute number. Each model in the catalog advertises its own pricing_skus, supported resolutions, durations and aspect ratios through GET /v1/videos/models. Sume docs describe billing as the provider list price times 1.25 on every model.
The Sume docs reviewed for this post do not name a Kling V3 or O3 id for POST /v1/videos, so do not assume one: list the catalog and confirm the id you want exists before you plan around it. If it is absent, the comparison is between the vendor's price and whichever catalog model you would use instead.
curl "https://api.sume.com/v1/videos/models" \
-H "Authorization: Bearer $SUME_API_KEY"
# read id, supported_resolutions, supported_durations and pricing_skus per modelSources
Related posts
More in Comparisons
- Live avatar agent or rendered video: D-ID vs Sume
D-ID V4 Expressive Visual Agents are live, LLM-connected avatars. Sume avatar video is rendered from a script in 4 to 60 s. Which one fits which job.
- LTX-2.5 license ($10M ARR line) vs hosted video ids
LTX-2.x Community license is free under $10M ARR and paid above it. Here is what changes if you call a hosted Sume video id instead of running weights.
- LTX-2.5 Fast 20 s vs Pro 10 s: long takes on Sume
LTX-2.5 Fast runs up to 20 s at 720p and 1080p, Pro 6 to 10 s. Sume lists no LTX id, but wan-3.0 and seedance-2.5 take single clips up to 30 s.
- Luma API callbacks and credit balance vs Sume webhooks and /v1/balance
Luma's docs list callbacks and a credits balance. Sume has webhook mode, GET /v1/balance, and a generation_limits snapshot. How to use each before a batch.
Written by Sume