Qwen-Image at $0.02 per megapixel vs a flat price per image
fal bills Qwen-Image per megapixel, rounded up, so a 1024x768 render counts as one. What that means when Sume prices the same model per image.
fal charges Qwen-Image $0.02 per megapixel, billed rounded up to the next whole megapixel, so a 1024x768 image (0.786 MP) is billed as one megapixel. Sume lists the same family as qwen/qwen-image and bills a catalog price per image, not per megapixel, so the quick way to compare is to read the endpoints record for the model rather than multiply pixels.
fal's price and features are from Qwen-Image on fal and Qwen Image Max on fal, both read 2026-10-03. Sume's billing model is from the Image API docs.
Per megapixel vs per image
On fal, Qwen-Image is described as strong at complex text rendering and precise image editing, with commercial use permitted and LoRA fine-tuning supported. Qwen Image Max is priced at $0.075 per generation on its fal page, which describes it as improving realism and naturalness over earlier versions.
| Model | fal price | Billing unit |
|---|---|---|
| Qwen-Image | $0.02 | Per megapixel, rounded up |
| Qwen Image Max | $0.075 | Per image generation |
Check the Sume price in one request
Sume publishes one endpoint per model, and the docs say its pricing lines already include Sume's margin. Run the script for the plain model and again for qwen/qwen-image-max, then compare the two lines.
import os
import requests
key = os.environ["SUME_API_KEY"]
url = "https://api.sume.com/v1/images/models/qwen/qwen-image/endpoints"
resp = requests.get(url, headers={"Authorization": f"Bearer {key}"}, timeout=30)
resp.raise_for_status()
body = resp.json()
body = body.get("data", body)
for endpoint in body["endpoints"]:
for line in endpoint["pricing"]:
print(endpoint["provider_slug"], line["billable"], line["unit"], line["cost_usd"])
Limits
A flat per-image price means a small render and a large one cost the same on Sume only if the catalog line does not vary by size, and the docs do not say it varies, so verify with usage.cost on a real call. LoRA fine-tuning is a fal feature: Sume's request schema has no LoRA field, and provider.options must be empty, so a custom Qwen LoRA is not something you can run through Sume.
Sources
Related posts
More in Pricing
- Real-time AI avatar pricing: live minutes vs one render
Live avatars bill by conversation minute and concurrent stream; a rendered clip is paid once and watched by anyone. Tavus plan numbers and the break-even.
- Recast with four people costs the same as one: photos are free
h3-max-recast bills source seconds only; fal includes reference images at no charge. A 10-second clip is $3.75 at 768p on Sume with one photo or four.
- Recraft V4.1 Pro costs $0.21 an image: is it on Sume?
Recraft lists V4.1 Pro at $0.21 and 12 seconds against $0.035 for standard V4.1. What that gap buys, and which Recraft id Sume's docs list.
- Reel at 181 seconds: Timeline bills four minutes, keep it at 180
One second over 180 turns a $0.30 Timeline render into $0.40 and a Reel that may not fit. How the ceil(minute) rule works and how to cap it with the plan call.
Written by Sume