What each channel publishes, column by column

A rate is one column. Beside it the register keeps seven more: unspent credits, the unit a page meters in, the price of a credit, the step between resolutions, parallel generations, the condition printed on a figure, and the longest single generation. Each entry below is one channel in one of those columns. As of 2026-09-12.

An entry exists for one of two reasons. Either the channel wrote something specific in that column, or its silence there is odd for its own class of seller. Both are findings; a blank cell that looks exactly like every neighbouring blank cell is not, and gets no page.

That rule leaves gaps on purpose. Five reseller channels print a rate and say nothing about how long one generation may run, which is the ordinary behaviour of that group rather than a fact about any one of them, so it is written up once as a question instead of five times as an entry.

Every entry carries the address it was read from and the day it was read, and sets the channel against the others answering the same column. The rate itself stays where it was, on the channel's own page, because a column entry is about one answer rather than about a product.

1Where unused credits go

• Runway credits — Runway answers this three times over, once per plan, and a fourth time for credits bought outright.
• Kling credits — Kling puts a 180-day window on each developer package and states plainly that it will not be carried forward or extended.
• invideo credits — One sentence settles it: credits do not roll over to the next month.
• Pika credits — Pika answers with a feature line rather than a rule, and the line covers purchased credits while leaving the monthly allowance unaddressed.
• SceneMixer credits — Membership credits join the same balance as purchased ones and spend identically.
• Morph credits — The pricing page raises the question in its own FAQ and the answer does not appear in the page text.
• Hedra credits — Three plan prices against three allowances make a credit cost divisible, while the FAQ asks whether credits survive the month and never says.
• HeyGen credits — HeyGen answers by billing cycle: monthly buyers keep credits one extra month, annual buyers accumulate to renewal, and cancellation ends both.
• Magnific credits — A year of validity with no monthly reset is the most generous answer in this column, and it sits beside credit figures that cannot be priced.
• Synthesia credits — Alone in this column, Synthesia never raises the subject where its plans are priced, despite selling credits with a stated equivalence in minutes.

2What the meter actually counts

• What fal meters — Output units, which means seconds on most video models and a whole clip on at least one, compared against an assumed five-second average.
• What Replicate meters — Most models are billed by how long they take to run.
• What Novita meters — One page, two meters: one model family priced by the second with audio as a step, two others priced per clip at named durations.
• What Segmind meters — GPU time by the hour and by the second, plus a per-run price banded by inference steps.
• What Synthesia meters — Credits, with a stated equivalence in minutes of video.
• What HeyGen meters — One credit currency for video and assets alike, with the page stating that the number a video consumes varies by model, duration and complexity.
• What Magnific meters — Credits against named durations at named resolutions, which is precise per model and converts into money nowhere on the page.

3What a credit costs, where it is said

• SceneMixer credit price — Between $0.0149 and $0.0078 depending on the pack bought, which makes the same credit rate a range in dollars rather than a figure.
• PixVerse credit price — A reference of 225 credits to the dollar with no packs listed, which makes the credit rate convert without choosing a volume first.
• Runway credit price — A cent a credit, printed on the same page as the twelve-credit rate, so the conversion needs no second document and no guesswork about volume.
• Luma credit price — Not stated anywhere on the pricing page, which leaves a credits-per-second rate that is exactly half of a usable figure.
• Pika credit price — Not stated, and the credit figures are attached to features rather than seconds, so two halves of the conversion are missing rather than one.
• Hedra credit price — Not stated, though three plan prices sit beside three allowances, so the figure divides out at a cent falling to about half that.

4What the step up in resolution costs

• MiniMax resolution step — Half again from 768P to 2K on one model, and about sixty per cent from 480P to 768P on the other.
• Vidu resolution step — Three and a half cents at 540p to seven and a half at 1080p, which makes it the flattest three-tier resolution curve on the ledger.
• Veo resolution step — Nothing at all from 720p to 1080p on the standard tier, and twelve times from the lightest model to 4K.
• Sora resolution step — Ten cents to seventy across two models and three resolutions, and a batch tier that halves every one of those figures at once.
• Wan resolution step — A clean doubling at each step, five cents to ten to twenty, so the top tier costs four times the bottom one on one model.
• Kling resolution step — Roughly double from 720p to 1080p, then a five-fold jump to 4K, and the first step is published as a band rather than per tier.
• Replicate resolution step — Nine cents at 480p against twenty-five at 720p on the same model family, which is the steepest single step on the ledger.

5How many generations may run at once

• Vidu concurrency — Five sessions free, and each one after that is priced as a line item at about $2,080 a month.
• Kling concurrency — Twenty per developer package, while the consumer membership page describes unlimited concurrent tasks.
• SceneMixer concurrency — A free account runs three generations at once and the paid tiers five to twenty, with a priority queue on the top three; the count covers every job.
• HeyGen concurrency — Published as a multiple rather than a figure: one tier is described as having twice the concurrency of the tier below, with neither quantified.

6The condition printed beside the rate

• Vidu price condition — Off-peak generation is stated at half the normal price, which puts a conditional floor under every tier on the page rather than one.
• Sora price condition — A batch tier at half the standard figure, applied to every model and every resolution on the page rather than to one of them.
• Runware price condition — One cell carries a struck-through five cents, then two and a half, labelled as a saving of about half.
• WaveSpeed price condition — One sentence says prices may vary with resolution and generation parameters, and it applies to every figure on the page including the cheapest here.

7How long one generation may run

• SceneMixer clip ceiling — Thirty seconds on two model families and fifteen on two others, stated per tier beside the rate rather than left to be discovered.
• Wan clip ceiling — Thirty seconds for one generation, stated in the model documentation, which is the long end of everything published here.
• HeyGen clip ceiling — Published in minutes rather than seconds, and by tier: up to thirty below one tier, up to sixty on it, with no stated limit above.

A column earns a place here once at least three channels have said something in it that a buyer could act on. Anything answered by one seller alone stays on that seller's own entry.

Elsewhere on the ledger: Channels, Ratings, Unpriced, Price shapes, One model, several sellers, Single ratings, Questions, Terms, Learn, Data. How a figure earns a line is set out on the method page.