AI&Design
All change articles

Grok · Official source

xAI raised Grok Imagine's image-edit API limit from three source images to five

The August 28, 2026 developer release notes increased the number of source images accepted in a single Grok Imagine API edit from three to five. On the documented direct route, POST https://api.x.ai/v1/images/edits, the request names grok-imagine-image-2.0 and passes an ordered images array. An edit can reference distinct pictures as subject, setting, style or composition and describe how to combine them in one prompt. The API guide says the first image supplies the default aspect ratio and the caller can override it with aspect_ratio. The guide displays three selectable source pictures with edited results for two- and three-source combinations. It provides a smaller example of how to structure the request. August 28 developer release notes · Multi-image editing guide

What gateway operators observed

Route and test dateThree source imagesFour source imagesFive source images
YM2API Site 2, September 17HTTP 200, one 1024×1024 JPEGHTTP 400HTTP 400
ArgoLink, October 9Included in operator methodsHTTP 400, no charge reportedNo trial specified

YM2API ran a descending series on its own /v1/images/edits endpoint using grok-imagine-image-2.0. Requests with 15 through four references each returned HTTP 400, with an error that specified a maximum of three. At three inputs the gateway returned HTTP 200 and one 1024×1024 JPEG. The operator says the image represented the numbers 1, 2 and 3 once each and included an empty quadrant. That three-source control establishes that the edit route could complete an edit during the test and that the requests at the two new counts were rejected. YM2API's JSON adapter uses images[].image_url and its own request validation. The guide gives the test date and reports the results in its reference-count section. Individual request and response records are unavailable. YM2API guide, sections 2, 5 and 8.1

ArgoLink reports sending one-, three- and four-source edits to its own gateway on October 9 with the same model identifier. Its four-source request returned HTTP 400 with an error identifying a three-source maximum. The operator reports no charge for that rejection and publishes the error and method. The count tests use the gateway's API and there is no reported five-source trial. The article separately attributes the direct xAI limit to xAI's guide. These two operator reports show that the input count accepted on a named gateway can differ from the documented count on xAI's direct API. ArgoLink methods and fourth-reference error

Evidence through the study cutoff

The signed-out August 21–September 11 Reddit search found no dated submission with the exact input count and an API result. The wider search identified an in-window client integration release on September 2. It says the project's xAI script added five-reference editing, up from three. The release has no paired execution and output. In the broader signed-out public search, the fal edit playground showed an output tied to a single source and fal's product page documented a three-input maximum for its own route. A published number of outputs, a montage with several objects, or a client schema that allows five attachments leaves the actual source count of a completed request open. Client release · fal model page · fal playground

The August 28 entry is the release anchor. By the November 18 cutoff, the public sources checked supplied dated evidence for rejected four- and five-source requests on YM2API and a rejected four-source request on ArgoLink. A completed four- or five-source edit with its input count and API result remains unverified.