How many aspect ratios each Sume image model lists, vs Hy's 14

Tencent's Hy Image 3.5 Preview lists fourteen aspect ratios, according to its OpenRouter page (read 2026-10-08). Sume does not list Hy Image 3.5. Among the image models Sume does list, Nano Banana 2.1 and the Ideogram rows list 15 ratios, Grok Imagine and the Flux, Qwen and Recraft rows list 13, and ChatGPT Image 2.5 lists 9.

Counts by row

The counts come from the per-model aspect lists that back GET /v1/images/models, where each row publishes an aspect_ratio descriptor with its allowed values. Counts include auto where the list has it. The lists differ in shape as well as in length, so a longer list is not always better for your layout.

Reading the table

Length is a poor proxy for fit. Ideogram's 15 values include tall ratios such as 1:3 and 10:16 that no Flux or GPT row lists. Nano Banana 2.1 is the only row with the 8:1 and 1:8 strips. GPT Image 2.5 has the shortest list among the edit-capable rows, but it also accepts custom pixels through image_size, so the list is not its ceiling.

Grok Imagine's list is tuned to phone screens, with 19.5:9, 9:19.5 and 9:20, and it has no 4:5. Imagen 4 has five ratios and no custom pixels.

Check a ratio in code

Do not copy this table into your app. The catalog is the source of truth and it changes. Read the descriptor at runtime and fall back to a row that lists your ratio.

import os, requests

H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}
want = "9:20"
r = requests.get("https://api.sume.com/v1/images/models", headers=H, timeout=30)
r.raise_for_status()
for m in r.json()["data"]:
    ar = m["supported_parameters"].get("aspect_ratio", {})
    if want in ar.get("values", []):
        print(m["id"], len(ar["values"]))

What the Hy page does and does not say

The OpenRouter listing says fourteen options including 1:1, 16:9, 9:16, 4:3 and 3:2. It does not name all fourteen in the text we could read, so we make no claim that a particular unusual ratio is or is not on its list. If you need a ratio from Hy, check the vendor page before you plan around it, and check Sume's descriptor for the row you would use instead.