CometAPI’s Runway and Kling price cuts call for different budget updates
How much should a video-generation budget change after CometAPI’s latest pricing notice? The answer depends on which models account for the spending. A September 24 update reduces Runway prices by 20% and Kling prices by 5%, so applying one headline discount across a mixed video workload would misstate the saving. The useful decision is to recalculate each portion of the budget before reconsidering model choice.
In its official changelog, CometAPI says Runway pricing has moved to 80% of previous prices and the Kling model series to 95%. Both changes took effect immediately. The same dated entry announces Runway Gen-4.5 availability, but the pricing change is a separate reason to revisit existing plans: a new model option and a lower rate answer different purchasing questions.
Consider an illustrative budget that previously allocated $100 to Runway generation and $100 to Kling generation. If the same usage remains billable on the same basis and the announced multipliers apply, those portions become $80 and $95. The combined saving is $25, or 12.5% of that $200 budget. This is arithmetic based on the notice, not an observed invoice or a prediction for every account. A budget dominated by Runway would be affected more than one dominated by Kling.
The reductions also change the economics of a fixed spending cap. Under otherwise identical billing conditions, a Runway budget could cover 25% more of the same billable generation, while a Kling budget could cover roughly 5.3% more. That does not mean either service becomes faster, produces more usable clips per attempt, or improves output quality. Those would require evidence beyond a rate announcement.
There are limits to what this notice establishes. It does not provide the old and new absolute rates, enumerate every affected configuration, or explain billing conditions for duration, resolution, unsuccessful jobs, or retries. It also gives no end date. Readers should therefore treat the announced percentages as a change relative to previous CometAPI prices, without assuming a discount against a vendor’s direct pricing or a permanent price guarantee.
For an existing video budget, my recommendation is to keep the intended output requirements constant and compare the current quoted price for each relevant configuration with the previous budget assumption. Then consider whether the resulting saving changes the allocation. A price cut can justify revisiting spending, but it cannot establish that Runway or Kling is the better creative choice. The September update supplies a reason to redo the calculation; the decision still depends on the outputs the project needs.