Hy Image 3.5 reference limit: 5 or 20, and Sume's caps

Hy Image 3.5's sources disagree on references: 5 in the announcement, 20 in the API guide. Sume's caps differ by model; read input_references from the catalog.

3 min readSume
All posts

The Hy Image 3.5 preview accepts 5 reference images in the announcement but up to 20 in the API guide, according to CellCog's write-up. When sources disagree, test the limit yourself. On Sume, the reference cap is a per-model value you read from the catalog, and the documented examples range from 5 to 16.

What the preview post says

CellCog's preview post reports a September 22, 2026 preview, $0.024 per image internationally, up to 4096 by 4096 output (other documentation conflicts and says 2K), a 100k-token prompt, a proprietary model with no weights, and the 5 versus 20 reference conflict.

Hy Image 3.5 preview facts and conflicts (read 2026-10-03)
ItemReported
Preview dateSep 22, 2026
Price$0.024 per image, international
Output sizeUp to 4096x4096 (docs conflict with 2K)
Prompt size100k tokens
References5 in announcement, up to 20 in API guide
WeightsProprietary, none released

Reference caps on Sume

Sume's Image API publishes capability descriptors per model, so you can read the real limit before you call. In the docs: ChatGPT Image 2.5 supports up to 16 image references, Ideogram 4.5 uses the first image for editing plus up to 4 more (5 total), and the sample descriptor for Seedream 4.5 shows input_references from 0 to 10. A model whose descriptor is {"min": 0, "max": 0} is text-to-image only and rejects references.

I did not find a Hy Image id in the Sume docs I read, so check GET /v1/images/models for current availability.

Reference caps in Sume docs (read 2026-10-03)
ModelReference cap
openai/gpt-image-2.5Up to 16
ideogram/ideogram-v4.55 total (1 edited plus 4 more)
bytedance-seed/seedream-4.5 (sample descriptor)0 to 10

How to settle a conflicting limit

  • Send a request with the larger number and read the error message.
  • Record the limit and the date you tested it.
  • Design your product for the lower number so a change upstream cannot break it.
  • On Sume, read supported_parameters.input_references instead of testing.

Sources

Related posts

More in Models

All Models posts

Written by Sume