Imagen 4 API shut down in the Gemini API: what Sume's catalog lists
Google says Imagen is shut down in the Gemini API and points to Nano Banana. Sume's image catalog lists google/imagen-4-fast, imagen-4-ultra and Nano Banana ids

Google's Gemini API docs state that Imagen is shut down there and tell developers to migrate to Nano Banana. Sume's image catalog code still lists google/imagen-4-fast and google/imagen-4-ultra alongside google/nano-banana-2 and google/nano-banana-pro, so what you can call on Sume is decided by Sume's catalog, not by Google's page.
Google's statement is from its Imagen page; Sume's from the Image API docs and catalog code, read 2026-09-29. Confirm with GET /v1/images/models, because a catalog can change.
What does Google say?
Its Imagen page reads: "Imagen is Google's legacy image generation model. It is now shut down and no longer available in the Gemini API." It says to migrate to Nano Banana, using gemini-2.5-flash-image or newer Nano Banana models in place of Imagen model names.
What are the Imagen rows on Sume?
Neither lists a 4:5 ratio, and their aspect ratios are the five below. Check GET /v1/images/models for whether a model accepts input_references.
| Model id | Input references | Ratios | One image |
|---|---|---|---|
google/imagen-4-fast | None | 1:1, 16:9, 9:16, 4:3, 3:4 | $0.03 |
google/imagen-4-ultra | None | 1:1, 16:9, 9:16, 4:3, 3:4 | $0.08 |
What should new work use?
If you need reference images or a 4:5 ratio, use a model that lists them; both Nano Banana ids list 4:5 and accept up to 10 input_references. Nano Banana Pro vs Nano Banana 2 explains the choice.
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": "A lighthouse in a storm, oil painting", "aspect_ratio": "16:9"}'Will my old Imagen model id keep working?
Sume's docs make no promise about future availability. Check the catalog before relying on any id.
Sources
Related posts
More in Models
- Kling 2.6 vs 3.0: length, resolution, audio and price
Kling 3.0 makes 3–15 s clips up to 4K with audio and multi-shot; 2.6 makes 5 or 10 s shots at 720p or 1080p. Kling's own specs and prices, dated.
- Kling 3 4K API: Kling's own tier and what Sume lists
Kling 3.0 lists 4K on Kling's own capability map, but Sume's kling-3 lists 720p and 1080p and prices no resolution tier. Sume's 4K route: gemini-omni-flash-1.1.
- Kling 3 duration and aspect ratio limits: Kling's own vs Sume's
Kling's own map lists 3 to 15 seconds for Kling 3.0; Sume's kling-3 takes 4 to 15 seconds at 16:9, 9:16 or 1:1. Values outside the list are refused.
- Kling 3 first and last frame API: request, limits and a gotcha
On Sume, kling-3 takes a first and optional last frame via frame_images, for 4-15 seconds. Send frame one in the shape you want; aspect_ratio is text-only.
Written by Sume