nano-banana-2 still works on Sume: it runs as Nano Banana 2.1 at 10c

Nano Banana 2 is retired on Sume, but the ids nano-banana-2 and google/nano-banana-2 still work. Sume runs them as Nano Banana 2.1 (google/nano-banana-2.1) and stores the 2.1 id on the job. The retired id is not in the model catalog, and a 2.1 image bills 10 cents.

What changes for an old integration

Nothing breaks, but two things shift under you. The model on the job is now 2.1, so a stored job's model field will read the new id. And your cost is the 2.1 rate, which the catalog gives as $0.08 list at 1K, times 1.25, equals 10 cents billed.

Why to update the id anyway

Sume accepts bare Image Router ids such as gpt-image-2 and nano-banana-2.1 as aliases for their org/slug equivalents, so there is no urgency. But a pinned id in your code and logs should say what really runs. If you compare outputs across weeks, two jobs both labelled nano-banana-2 would be the same 2.1 model, and a log that says 2.1 is easier to audit.

The fix is a one-line change in each call: use google/nano-banana-2.1. Look up the live descriptor with GET /v1/images/models/google/nano-banana-2.1/endpoints to confirm ratios and price. Ratios listed on 2.1 include 4:5, 9:16, 16:9 and the long ones 4:1, 1:4, 8:1 and 1:8.

• Resolution tiers on 2.1: 0.5K, 1K, 2K, 4K, with charges that scale away from 1K.
• Up to 4 images per call; edits are supported.
• If you want the Pro row instead, change the id to Nano Banana Pro and expect 19 cents.

Search your code

Grep for nano-banana-2 in config files, prompts and stored job records, then replace the id. Keep a note of the date, since runs before and after the retirement of the old model may differ in look even with an unchanged prompt.

What to tell your team

Tell them three things. The old id still works. The model that runs is 2.1. The bill is 10 cents at 1K per image, so 1,000 images are $100 and 10,000 are $1,000. If anyone relied on the earlier model's output style, regenerate a small sample on 2.1 before the next campaign.

The retired id is not in GET /v1/images/models, so a dropdown built from the catalog will not show it. Anything that still sends it keeps working, which is exactly why it can linger in old scripts for months.