Luma layers API: 10 RGBA layers vs Sume's flat image result
Luma type layering splits one image into up to 10 ordered RGBA PNG layers. Sume returns flat images at data[].url; n counts images, not layers.
Luma's layering type splits an existing image into up to 10 ordered RGBA PNG layers, back layer last. Sume's Image API has no layering call: it returns flat images at data[].url, and n sets how many images you get, not layers.
Luma facts are from its Image layering guide and its July 29, 2026 news post; Sume facts are from Image models, read 2026-10-01.
What does a Luma layering request return?
| Item | What the guide says |
|---|---|
| Request | type: "layering", a source image, and a prompt |
prompt | Required by the schema, may be an empty string, at most 500 characters |
| Result | Up to 10 outputs, ordered front to back; the last is the opaque background |
| Each layer | A PNG cropped to its visible content, with layer.bounds for placement |
| Layer count | Chosen by the planner; the prompt steers grouping |
How do I call it?
Send a source image by URL, base64, uploaded file or a prior generation id. A minimal request:
curl -X POST https://agents.lumalabs.ai/v1/generations \
-H "Authorization: Bearer $LUMA_AGENTS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"layering","model":"uni-1","prompt":"","source":{"url":"https://example.com/poster.jpg"}}' What does Sume return instead?
Each image is one file at data[].url (Sume-hosted, signed). n takes up to 10 images per call, per-model ceilings lower, and they are separate generations, not parts of one scene. Edits go through input_references, which the docs describe as reference images for image-to-image.
The Image API parameter table lists no layering or decomposition option.
What can I do on Sume when I need separate elements?
Generate the elements as separate images with their own prompts and compose them in your own editor, or do the split with a layering service. The same gap is covered for other models in Ming Image design layers and Ideogram layerize.
Sources
Related posts
More in Models
- Ray 3.2 API aspect ratios and resolutions, and Sume's lists
Luma lists six Ray 3.2 aspect ratios (9:16 to 21:9) at 540p, 720p and 1080p. Sume reports ratios per model in supported_aspect_ratios and rejects size.
- Luma Scenes Ray 3.2 or Seedance 2: pin a model or use auto
Luma says Ray 3.2 and Seedance 2 are not interchangeable. On Sume, pin a catalog model for a known clip length, or send sume/auto and let Sume pick.
- Seedance 2.0 4K price: Luma 261 credits/sec, Runway 150, Sume 1080p
Luma lists Seedance 2.0 at 4K for 261 credits per second; Runway's docs list 150. Sume's docs list seedance-2 at 480p, 720p and 1080p, with no 4K entry.
- Luma uni-1 API: image models, types, and what Sume lists
Luma's API has two image models, uni-1 and uni-1-max, each with image and image_edit types. Sume lists its own catalog; check the models endpoint.
Written by Sume