Cost of 1,000 AI images on Sume: Soul, Flux 2 Pro, Grok, Nano Banana 2

A thousand single-image jobs cost $10 on Higgsfield Soul, $40 on Flux 2 Pro, $30 on Grok Image and $100 on Nano Banana 2, from Sume's catalog prices.

3 min readSume
All posts

One thousand single-image jobs cost $10 on Higgsfield Soul, $30 on Grok Image, Qwen Image and Imagen 4 Fast, $40 on Flux 2 Pro, $50 on Seedream 5 Lite and $100 on Nano Banana 2 on Sume. These are flat per-image prices from the generated catalog.

Where the prices live

The public catalog is generated into packages/api-contract/src/generated/catalog-cents.ts and listed on the API pricing page. Each is the provider list price times 1.25, rounded up to the cent per job, and I computed the cents with the estimators in media-estimators.ts.

Billed per image and per 1,000 single-image jobs (read 2026-10-06)
ModelPer imagePer 1,000 images
higgsfield-soul$0.01$10
seedream-5-lite$0.05$50
flux-2-pro$0.04$40
grok-image$0.03$30
qwen-image$0.03$30
imagen-4-fast$0.03$30
nano-banana-2$0.10$100

Caveats

A thousand is a thousand jobs. Models that bill by quality or size, such as GPT Image 2.5 or Ideogram 4.5, are not in this table because their prices vary; see the GPT Image 2.5 per-1,000 post for those. Price tells you nothing about quality, so test your prompt before scaling.

Round-up matters at this scale. Soul's list price is $0.004, which would be $4.00 per thousand, but each job bills a whole cent, so a thousand jobs cost $10. See the price-list post for the margin rule.

  • Prices are per job, so a thousand jobs is 1,000 times the cents.
  • Check the image models docs for limits.

Picking by budget

With a $100 budget, you could make about 1,000 Nano Banana 2 images, 2,500 Flux 2 Pro images, 3,333 Grok Image images or 10,000 Higgsfield Soul images. The cheapest model is not always the best for a given look, so spend a few dollars on a comparison set of 20 prompts across two or three models before committing a thousand.

Prices can change with the provider list, which Sume multiplies by 1.25. These figures were computed from the pricing code on 2026-10-06, and the public price list on the API pricing page is the place to confirm current numbers before a large run.

How these numbers were produced

I read the rate tables in the clone of Sume's repository on 2026-10-06 and called estimateImageRouterProviderCost for seven image models, covering one image each at default settings. The output fields are billableAmountUsdMicros and billableAmountUsdCents; the tables show the cents.

These are estimates of the billed amount for the stated settings. Anything not in the table, such as a different frame shape, a reference input or a changed quality tier, can change the number, so run the estimate for your own request before a large batch. Where this page and the public API pricing list disagree, the pricing page and the live quote win.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume