FLUX.2 Turbo $0.008 per megapixel: what Sume lists for FLUX.2

fal's FLUX.2 Turbo page lists inference at $0.008 per megapixel, while Black Forest Labs' own page lists FLUX.2 [pro] from $0.03 per megapixel and [flex] at $0.06 per megapixel. Sume's image catalog in the repo lists black-forest-labs/flux.2-pro and black-forest-labs/flux.2-flex, not a Turbo id, so on Sume you pay the catalog's per-image line for pro or flex.

Vendor numbers come from FLUX.2 Turbo on fal and the FLUX.2 overview, both read 2026-10-02. Sume's side is from the Image API.

What do the vendor pages say?

fal describes FLUX.2 Turbo as text-to-image generation with FLUX.2 [dev] from Black Forest Labs with enhanced realism, crisper text and native editing at turbo speed, priced at $0.008 per megapixel, with commercial use permitted. Black Forest Labs lists [klein] from $0.014 per image, [max] from $0.07 per megapixel, [pro] from $0.03 per megapixel, [flex] at $0.06 per megapixel and [dev] as free for non-commercial use.

Why can't you compare them to Sume's price directly?

Vendors quote per megapixel; Sume's catalog publishes a per-image line in the endpoint record, for example { "billable": "output_image", "unit": "image", "cost_usd": 0.033 } in the Seedream example on the Image API page. The page says Sume's margin is already applied to that figure, so what you see is what you pay.

To compare, convert: a 1024x1024 image is roughly 1.05 megapixels, so a per-megapixel list price turns into about that many dollars per image before margin. Then read Sume's real line from the catalog, since margin and rounding apply there. The earlier post on list times 1.25 shows the arithmetic.

How do you read the live number for a Sume FLUX model?

Ask the catalog; do not trust a blog post, including this one, for a price that changes.

curl -s "https://api.sume.com/v1/images/models/black-forest-labs/flux.2-pro/endpoints" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  | python3 -c "import sys,json;print(json.load(sys.stdin)['endpoints'][0]['pricing'])"

So should you wait for a Turbo id on Sume?

Not unless speed or cost per megapixel is your bottleneck. The repo's catalog has pro and flex, which Black Forest Labs describes as production-grade and typography-oriented respectively. If you need Turbo today, call fal directly; if you want one wallet and one job format, use pro or flex and track the catalog for new ids with a diff job. For the price of FLUX.2 pro and flex per image see FLUX.2 API pricing.

A tiny cost worksheet

The worksheet is deliberately boring. Prices move, models are renamed, and a pasted number goes stale in weeks, so recompute from the live pages when you plan a budget.

• Pixels: width times height divided by 1,000,000 gives megapixels.
• Vendor list: megapixels times the per-megapixel price on the page.
• Sume: read pricing[0].cost_usd from the endpoint record; margin is already included.
• Monthly: images per month times the figure from the step above.