Nano Banana 3: does it exist? Current ids
Google autocomplete suggests a Nano Banana 3, but suggestions are not releases. What autocomplete lists and which Nano Banana id Sume accepts.

Autocomplete showing "nano banana 3" proves people search for it, not that a model with that name exists. On the read date, Google's suggestions for "nano banana" included 3 alongside pro, 2, gemini, ai, 2 pro, free, 2 lite and api. Do not put a guessed id into an API call; read the model list of the platform you call.
What the suggestion list shows
The table is the autocomplete response for the query "nano banana" on the read date. Order and wording are Google's and change over time, so this is evidence of interest and of naming patterns only.
| Suggestion | What it indicates |
|---|---|
| nano banana pro | A Pro variant is searched |
| nano banana 2 | A second version is searched |
| nano banana 2 pro | Version and Pro combined |
| nano banana 2 lite | A lite tier is searched |
| nano banana 3 | Searched; not a confirmation of a release |
| nano banana api | People look for API access |
Which id Sume accepts
The Sume Image API page lists legacy bare ids, naming gpt-image-2 and nano-banana-2 as examples, and says they are accepted as aliases for their org/slug equivalents. That is the only Nano Banana id the docs name.
The docs do not name a Nano Banana 3 or other variants, so a request for one would not be something to rely on. The reliable check is the catalog: GET /v1/images/models lists the ids and pricing the endpoint accepts. A model that is not in that response is not available to you.
curl "https://api.sume.com/v1/images/models" \
-H "Authorization: Bearer $SUME_API_KEY"A rule for future model names
When a new name appears in search, check three things before changing code: the vendor's own announcement, the model list of your API provider, and the exact id string the list uses. Pin the id from the list, not from a headline.
If you want Sume to choose, sume/auto is the Sume-only model value for images. Sume picks the family and never discloses which one ran, so use a pinned id when you need repeatable output.
Sources
Related posts
More in Models
- Kling 3.0 allows 3 seconds at Kling; Sume's kling-3 starts at 4
Kling's guide lists 3 to 15 seconds for Kling 3.0. Sume's kling-3 takes 4 to 15, so a 3-second beat means a 4-second clip, then a trim.
- Kling 3.0 element references are not on Sume's kling-3: use these
Kling's guide lists start frame plus element reference for Kling 3.0. Sume's kling-3 refuses reference inputs; Seedance 2.0 and Wan 3.0 accept them.
- Does Kling 3.0 do 9:16? Its guide is silent; Sume lists 3 ratios
Kling's Kling 3.0 guide gives 720p, 1080p and 3 to 15 s but no aspect ratios. Sume's kling-3 row lists 16:9, 9:16 and 1:1. Read the catalog to confirm.
- Kling 3.0 multi-shot: Sume's kling-3 has no field, so cut on Timeline
Kling's guide describes automatic and custom multi-shot for Kling 3.0. Sume's kling-3 request has no multi-shot field; join separate clips with Timeline.
Written by Sume