RenderDrama

What a second of AI video costs, channel by channel

How long a single generation can be

SceneMixer publishes 30 seconds on its Wan 3.0 tiers and 15 seconds on its MiniMax H3 tiers, with H3 at about $0.16 a second and H3 Fast at about $0.10. Alibaba Cloud prints a 30-second ceiling for Wan 3.0 beside its rates. No other channel here states a ceiling on the page carrying its price. As of 2026-09-12.

What each channel puts on its pricing pageFilled where the channel publishes something in that column, hollow where its pricing page is silent.What each channel puts on its pricing pageFigureWhat it coversSceneMixer, Wan 3.0 tiersSceneMixer, Wan 3.0 tiers — Figure: 30 secondsSceneMixer, Wan 3.0 tiers — What it covers: Stated alongside the rateWan, Wan 3.0Wan, Wan 3.0 — Figure: 30 secondsWan, Wan 3.0 — What it covers: Stated alongside the rateSceneMixer, MiniMax H3 tiersSceneMixer, MiniMax H3 tiers — Figure: 15 secondsSceneMixer, MiniMax H3 tiers — What it covers: H3 about $0.16, H3 Fast about $0.10Every other channelEvery other channel — Figure: Not stated on the pricing pageEvery other channel — What it covers: Ceiling published elsewhere or not at all
Fig. 1 Filled where the channel publishes something in that column, hollow where its pricing page is silent.
The longest single generation each channel states on the page carrying its price. Recorded 2026-09-12.
ChannelFigureWhat it covers
SceneMixer, Wan 3.0 tiers30 secondsStated alongside the rate
Wan, Wan 3.030 secondsStated alongside the rate
SceneMixer, MiniMax H3 tiers15 secondsH3 about $0.16, H3 Fast about $0.10
Every other channelNot stated on the pricing pageCeiling published elsewhere or not at all

Inclusion rule. Ceilings stated on the same page as the price. A ceiling documented in an API reference separate from the price is not recorded here, because this ledger reads the pages a buyer sees before paying. Order. Channels that state a ceiling first, longest first.

1The ceiling belongs next to the price and rarely is

Two channels at the same rate with ceilings of thirty and fifteen seconds are not selling the same thing: the second one needs twice as many generations for the same minute and twice as many joins. A pricing page that omits the ceiling is omitting half of what determines cost.

This is the field where the gap between what is published and what a production needs is widest in the whole ledger, and it is also the easiest one for a vendor to close.

2Two tiers on the same channel can have different ceilings

The clearest case here has 30 seconds on one model family and 15 on another, at prices that overlap. A buyer choosing on rate alone can land on the shorter ceiling without noticing, and discover it when the first long shot has to be split.

Recording the ceiling per tier rather than per channel is the only way to show that. A channel-level figure would have to pick one and would be wrong for the other.

3Why the API reference is out of scope

Several vendors document a maximum duration in developer material. That is a real number and it belongs to a different reader: this ledger reads the pages somebody sees before deciding to pay, because that is where a buyer forms an expectation.

Where a vendor moves its ceiling onto the pricing page, the row changes and the date moves. Until then, not stated on the pricing page is the accurate description and it is what the cell says.

4Sources

Each figure is read from the vendor page linked in the ledger, checked 2026-09-12. How a figure qualifies is on method; what a rate leaves out is on limits and unspent credits and parallel generations. Nearby: Expiry, Concurrency, One model, four prices.