Image 1.0 and Image Router price band: 1 cent to $7.36 per call
Sume lists Image 1.0 and Image Router at 23 cents estimated, 1 cent minimum and $7.36 maximum. Learn what the maximum reserves and how transparency adds cost.
What does one Sume image cost, and what is the highest hold?
The catalog shows Image 1.0 and the Image Router at an estimate of 23 cents per call, a minimum of 1 cent and a maximum of $7.36. The rate card lists $0.2225 per image for Image 1.0, which is the figure behind the estimate.
The maximum is not a price per image. It reserves the largest request the endpoint accepts: max quality, auto size, 4 images and 16 reference images.
What are the three bands?
Bands are in USD cents, with the 1.25 margin applied.
| Band | USD | What it represents |
|---|---|---|
| Minimum | $0.01 | Router: the cheapest model in the catalog |
| Estimate | $0.23 | A default single image |
| Maximum | $7.36 | Max quality, auto size, 4 images, 16 references |
How does transparency change the cost?
Requesting a transparent image adds one background-removal pass per image. The rate card lists RMBG at $0.0225 per image, which the catalog rounds to 3 cents. So a four-image transparent request carries four extra passes on top of the generation price.
The images docs describe the request fields. If you generate first and cut out afterwards, the RMBG price is the same, so the choice is about workflow and not about savings.
Why is the minimum only 1 cent?
On the Image Router, the minimum reflects the cheapest model in the catalog, so it only applies if you choose that model. Image 1.0 at its list rate does not hit that number. Do not plan on 1 cent per image unless the model you request lists that price.
Sume does not guarantee a model's price stays at that level. Read the catalog again before you quote a client, and use the list-times-1.25 explainer to see how the multiplier works.
How should I size a wallet for an image batch?
Multiply your image count by the per-image price and add the cutout price where you need transparency. For example, 100 default images at $0.2225 come to $22.25 before any cutouts. Because each submit reserves its own estimate, the sum of in-flight jobs is what your balance needs to cover at once.
What does a worked example look like?
A product team wants 40 product shots with transparent backgrounds. Generation at $0.2225 each is $8.90. Transparency adds one RMBG pass per image at $0.0225, so $0.90 more, for $9.80 in total.
If they submit all 40 as single-image jobs and the plan allows 4 at once, only four reserves are open at a time, so the wallet needs about $1 free to start. A single 4-image request with 16 references at max quality is a different shape and can reserve far more, up to the $7.36 ceiling.
Keep the request shape in your budget note, because the same endpoint prices very differently with different settings.
Sources
Related posts
More in Pricing
- Kling motion control duration_seconds: it sets the credit hold
On Sume's Kling 3.0 Motion Control, duration_seconds (1 to 30) sizes the credit reservation; the output length follows the driving video, not this field.
- The largest hold one Sume call can place: a wallet sizing table
Maximum catalog band per Sume endpoint, from 13 cents for music to $56.25 for a 300-second Fabric clip. Use the table to size a wallet for concurrent jobs.
- Luma modify video price: $0.60 vs $1.75 for a 720p 5-second clip
Luma prices Modify Video per million pixels: $0.00544 on ray-flash-2 and $0.01582 on ray-2. Worked example, and how Sume quotes a clip.
- Luma Ray 3.2 API price per second: 540p, 720p and 1080p
Luma lists Ray 3.2 text and image to video at $0.15, $0.30 and $1.20 per 5-second clip at 540p, 720p and 1080p. The per-second math, and 10-second clips.
Written by Sume