Audit a rival price-per-second table against the vendor pages

Treat any vendor-authored price table as a lead, not a fact, and check each row on the seller's own page. A Higgsfield comparison dated September 2026 lists Veo 3.1 Standard at $0.40 per second, Runway Gen-4.5 at $0.12, Luma Ray 3.2 at $0.09, MiniMax H3 at $0.08 and Seedance 2.5 at $0.231 at 720p. Only some of those rows can be matched against first-party pages we read on 2026-10-03.

How the checks were done

Google's Gemini pricing page lists Veo 3.1 Standard at $0.40 per second for 720p and 1080p. For Runway, the pricing page gives Gen-4.5 at 60 credits per 5 seconds, which is 12 credits per second; plan credit prices of $0.0192, $0.0124 and $0.0080 give $0.230, $0.149 and $0.096 per second. The $0.12 row lands inside that range.

Rules for using rival tables

• Check the unit: per second, per clip or per credit.
• Check the plan or tier behind a credit price.
• Note who wrote the table; the Higgsfield post is vendor-authored and is itself a seller.
• Date every number and re-read before quoting it.

On Sume

Sume prices are provider list times 1.25, shown per model in pricing_skus from GET /v1/videos/models, so you can check them with one API call instead of trusting a table. See the video docs.