Nano Banana 2 pricing per image on Sume, by resolution tier

On Sume, one Nano Banana 2 image (google/nano-banana-2) is estimated at $0.10 at the default 1K tier, $0.08 at 512, $0.15 at 2K and $0.20 at 4K. The price is per image, so n images cost n times the tier price, and it is reserved from your wallet when you submit.

The numbers come from Sume's pricing code and the Image API docs, read 2026-09-29. The live figure for your account is the pricing line on GET /v1/images/models/google/nano-banana-2/endpoints.

How much does one Nano Banana 2 image cost?

The tier is set with resolution. Omit it and you get 1K. The estimate is what Sume reserves; a generation that completes is billed in full and one that fails is not billed.

How does that relate to Google's own price list?

Google publishes per-image prices for its own Gemini API on its pricing page. For its Gemini 3.1 Flash Image row it lists $0.045 at 0.5K, $0.067 at 1K, $0.101 at 2K and $0.151 at 4K. That page prices Google's API, not Sume's, and Sume's docs do not state which Google row a Sume model id maps to, so treat the two tables as separate price lists rather than one comparison.

What will my request reserve?

Sume reserves the estimate on submit. If the wallet cannot cover it, the submit returns 402 insufficient_credits and nothing starts, as listed in Errors and rate limits. A failed job's reservation is released or refunded where applicable.

curl -X POST https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "google/nano-banana-2",
    "prompt": "Studio photo of a green ceramic teapot",
    "resolution": "2K",
    "n": 2
  }'

Does a bigger tier take longer?

The image endpoint waits up to 30 seconds and then returns 200 with the images. If the job is still running it returns 202 with a job envelope instead, and 4K, high quality and large n are the ones most likely to do that. Check the status code, then poll GET /v1/jobs/{id}/status for a 202.