Which Sume Formats return images, not video? 9 of the 27 slugs

Of the 27 Formats by Sume at the reserved sume handle, 18 declare video output and 9 declare image output. The nine image slugs are sume-water-splash-hero, sume-model-product-portrait, sume-magazine-cover-campaign, sume-formula-texture-hero, sume-sunscreen-splash, sume-cream-squeeze, sume-serum-drip, sume-toner-pour, and sume-editorial-product-set. Read the io profile of any slug before you call it.

The split

The catalog page lists the callable slugs and says that any other slug answers 404 format_not_found at sume/{slug}. Each Format also carries an io profile: input_kind (url, text, image, or product) and output_kind (video, image, or text). The counts here come from Sume's first-party seed for these 27, which declares text input on all of them. Confirm the live profile with GET /v1/formats/sume/{slug}.

Why it changes your integration

The shape of what you store changes. A video run lands a media.sume.com MP4 in artifacts[], and an image run lands an image there. If your code assumes a video, primary_output_url for an image Format will still resolve to the first media object, but your player will fail. Branch on output_kind when you pick a slug from the list, not after the run.

Cost and time also differ. An image Format is a still, and a video Format makes clips, voice, and an assembly, so it takes minutes. Plan your timeouts and your spend cap per kind, and use a webhook for video.

Read before you call

The same call works for every slug. The path is POST /v1/formats/sume/{slug}/runs, the key needs formats:write, and the run and its spend belong to your key. Nothing is forked or installed. If you want to change the catalog Format, fork it in the Format library and call your copy at {your_handle}/{slug}.

io and showcase are both null for Formats saved before registration existed. That means not declared, not takes no input. For those, use the description.

curl -sS "https://api.sume.com/v1/formats/sume/sume-serum-drip" \
  -H "Authorization: Bearer $SUME_API_KEY"
# read data.io.output_kind before you POST .../runs

A routing rule for your code

If you build a picker, store the slug, the output_kind, and the date you last read the profile. When a user chooses a Format, show the kind first, so nobody expects a clip from a still Format. Re-read the profile on a schedule, because the catalog can change: the docs list the slugs callable today, and a slug off the list gives 404 format_not_found.

Do not infer input from the name. The run body's input is a free-form object by design, so the io profile is the only declared contract between a Format's author and its callers. A product Format may want a product image, and a text-input Format may want only an instruction.

Picking within the image group

Nine image slugs cover different jobs: splash and pour shots for liquids, a squeeze for creams, a drip for serums, a texture hero for formulas, a portrait with a model, a cover layout, and a coordinated product set. Pick by the physical action your product shows, then call it with one packshot. A page of your own with the same action is a fair test of whether the slug fits.