Do API price changes affect jobs already submitted? Sume

On Sume, the estimate is reserved when the request is accepted, then captured on success or refunded on failure. Here is how to read it in Usage.

4 min readSume
All posts

On Sume, the amount is set when the request is accepted: paid generation uses public Sume USD estimates, and at submit time Sume reserves the estimated amount. Successful completion captures the reserved usage. The sources read here do not describe repricing a job after it was accepted, so check the job's Usage row if a rate changed around your submit.

Why does this question come up?

Vendor prices carry dates. Runway's pricing page lists eleven_v4 at 2.2 credits per 1,000 characters until October 12, 2026 PT, then 5 credits per 1,000 characters. A script submitted before and finished after that date raises the question of which rate applies. Read the vendor's own terms for its behavior; this post covers Sume only.

What states does a Sume job's usage pass through?

The Usage docs define three states.

Usage statuses from the Sume docs, read 2026-09-30.
StatusMeaning
reservedEstimated usage was reserved before provider execution.
capturedBillable usage was captured after successful completion.
refundedReserved usage was released after failure or cancellation before capture.

What if the balance is too low at submit?

The submit is rejected with 402 insufficient_credits: Sume cannot reserve the estimated generation cost from the workspace balance. The check happens at submit, so an accepted job is not stopped later for that reason by the sources read here. Failed jobs and failed queue admission release or refund the reservation where applicable; see do failed AI video jobs cost money.

How do I avoid surprises around a price change date?

Submit before the date if the lower rate matters, read the reserved amount on the job, and compare it with the captured amount in Usage. For an example of a dated step-up, see Eleven v4 until October 12.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume