fal lists Nano Banana 2.1 at $0.040 for 1K: which price Sume bills

fal's Nano Banana 2.1 card shows $0.040, $0.059 and $0.134 by tier. Sume bills its own endpoint price, so read pricing on the Sume record, not the vendor card.

4 min readSume
All posts

fal's Nano Banana 2.1 card currently shows $0.040 for a 1K text-to-image call, $0.059 at 2K and $0.134 at 4K (read 2026-10-10). Sume does not pass that card through. You pay the pricing[].cost_usd value on Sume's own endpoint record for google/nano-banana-2.1, so read that number before you budget.

This post lays out the vendor card and shows how to pull the Sume number in one request.

What fal's card says

The figures below are from fal's Nano Banana 2.1 page, read 2026-10-10. fal describes them as representative costs for one output image from a short prompt with medium thinking.

  • Output image tokens are listed at $35.294 per million, input at $1.764 per million.
  • The card lists up to 14 input images on the edit endpoint, aspect ratios from 21:9 to 1:8, and 1 to 4 images per request. Check Sume's own endpoint record for the limits that apply to you.
fal Nano Banana 2.1 price by resolution (read 2026-10-10)
ResolutionSize on the cardText-to-image
1K (default)1 megapixel$0.040
2K4 megapixels$0.059
4K16 megapixels$0.134

Why the vendor card is not your bill

Sume's Image API says endpoint pricing lines are the amount Sume charges your wallet and already include the Sume margin, so you pay cost_usd x n. Sume also publishes one sume endpoint per model, and it does not name the upstream provider.

That means a change on a vendor card does not automatically change a Sume line, and the other way round. A fal price you saw this morning is a lead, not your invoice.

Read the Sume price in one call

Request the endpoint record and read the pricing array. The docs show the shape as a billable line such as output_image with a unit and a cost_usd value.

curl "https://api.sume.com/v1/images/models/google/nano-banana-2.1/endpoints" \
  -H "Authorization: Bearer $SUME_API_KEY"

Which tier to pick

Sume's resolution field is a normalized tier (512, 1K, 2K, 4K, per the Image API page), and whether a given row offers every tier is in its endpoint descriptor. Pixels grow four-fold from 1K to 2K and sixteen-fold to 4K, while the vendor price only rises about 1.5 times and then 3.4 times (0.059 over 0.040, 0.134 over 0.040). So on the vendor card the 2K step adds the most pixels per extra dollar.

Whether that ratio holds on Sume depends on the endpoint record, so compare your own tiers there before you move a batch.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume