Qwen Image 3.0: does Sume list it? A catalog check

Not under that name. As of 2026-09-29, Sume's image catalog lists two Qwen ids, qwen/qwen-image and qwen/qwen-image-max, and neither is labeled 3.0. Sume's docs do not say which Qwen release either id serves, so the ids cannot tell you whether a 3.0 model is behind them. This post makes no claim about a Qwen 3.0 release.

How do I check whether a new Qwen id appeared?

The catalog is the live list, and it changes without a docs update. Filter it for Qwen; an empty result means no Qwen model is listed at that moment. The call needs an API key, and a missing or invalid one returns 401 unauthorized.

curl -s "https://api.sume.com/v1/images/models" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  | jq -r '.data[] | select(.id | startswith("qwen/")) | .id'

What should I read on a new Qwen row?

If a new id shows up, its record tells you what it does before you spend anything. Follow the endpoints URL for the price.

What does a made-up Qwen 3.0 id return?

An id that is not in the catalog returns 404 model_not_found with the message Unknown image model id. and a catalog_url. It fails before generation, so nothing is billed.

curl -X POST "https://api.sume.com/v1/images" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "qwen/qwen-image-3.0", "prompt": "a chalkboard menu"}'

Which listed Qwen id should I use meanwhile?

Pick by the job: qwen/qwen-image also takes reference images, and qwen/qwen-image-max is text-to-image only; see Qwen Image Max on Sume. For why a similarly named open model is not an id here, read Qwen Image 2.1 API. The Image API docs explain the catalog descriptors.

Can the created field date a model?

No. Sume has no per-model creation timestamp, so every catalog row reports the same value, the catalog's own ship date. Do not read created as a release date for a Qwen model or any other. To tell one release from another, read the row's name, description and parameters, and the vendor's own page for anything about the model itself.

To watch for changes, run the filter above on a schedule, from CI or a cron job, and alert when the output differs from your last run. The list only includes models whose provider is configured at that moment, so a row can also disappear and return. Alert on any change, then read the new row before you send traffic to it. Keep the previous catalog snapshot so you can diff the two.