A percentage discount is not a price comparison. CometAPI’s September 24 video-pricing notice illustrates why: it announces Runway prices at 80% of their previous level and Kling-series prices at 95% of theirs. Those are different reductions from different baselines, not proof that one family is now cheaper for a particular video job.
The notice remains in CometAPI’s current changelog. On October 13, it is 19 calendar days old. It remains materially relevant as an ongoing pricing adjustment announced effective immediately, without a stated expiry; it should not be presented as a new announcement today. Nor does the notice, by itself, verify any particular account’s current invoice.
Preserve the denominator
The stated changes are a 20% reduction for Runway and a 5% reduction for the Kling series. To interpret either, the previous price is the essential denominator. A larger percentage reduction does not establish a lower absolute price when the starting prices differ.
Even a comparison using the same hypothetical starting price would be an illustration, not the actual catalog. The responsible reading is simply that the announced Runway rate becomes 0.80 times its own prior rate and the announced Kling rate becomes 0.95 times its own prior rate. This is arithmetic from the notice, not evidence from a billing test.
It is also not a discount measured against every upstream vendor’s official price. The wording specifies previous prices. Replacing that baseline with an assumed official-price comparison would make a different claim from the one CometAPI published.
The purchase unit still matters
The brief notice does not give a universal billing unit, absolute rate, or cost for a completed video. A buyer needs the applicable offered terms before comparing spend across model choices. Equal percentage language does not make seconds, requests, or outputs interchangeable units.
My recommendation is to keep the intended deliverable visible in the purchasing discussion. What must the finished asset accomplish? Which price applies to that choice? How are rejected attempts or requested revisions accounted for? These are decision questions, not claims that a particular model produces more revisions or instructions for running an experiment.
A lower rate can reduce one cost component without establishing a lower cost per usable asset. The notice supplies no acceptance-rate or revision data that settles that broader outcome.
Immediate does not mean permanent
CometAPI says both updates are effective immediately. That anchors the announced change to the September 24 notice; it does not guarantee that prices can never change again or that every account has identical terms. The absence of a stated expiry should not be converted into a permanent contractual promise.
The same dated entry adds Runway Gen-4.5, but that availability statement does not prove that the new model and every older option share identical economics or output quality. Keep the pricing adjustment separate from unsupported capability comparisons.
The takeaway is to use the two reductions as specific, attributable changes in a continuing cost baseline. For a video-product decision, the relevant offered price and the required usable asset still matter more than which discount percentage makes the bigger headline.