Logo animation API: from brand mark to ident or end card

To animate a logo with the Sume API, call the catalog Format sume-logo-motion-design at POST /v1/formats/sume/sume-logo-motion-design/runs with the mark as an image attachment, or animate the mark yourself as the first_frame of a POST /v1/videos request. To close a video with it, add the clip as the last slot of a Timeline 1.0 render.

Facts come from the Format catalog, Format API, Create a run, Video generation, and Timeline 1.0 docs pages, the Format's published description, and the OpenAPI document behind the Sume API reference, read on 2026-09-27.

What does the logo Format make?

sume-logo-motion-design makes “a finished logo motion video that reveals a supplied brand mark through clean material, light, depth, or graphic movement”. Its description lists “logo idents, brand stings, app intros, launch bumpers, and social end cards” and ends “Not for: static campaign deliverables”, so the result is a video.

The recipe is private. The run's model field picks only the orchestrating LLM; image, video, and audio models are chosen by the Format's tools. Animate only marks you own or have permission to use.

How do I send the logo?

Attach the mark as an input_image with a public HTTPS image_url, from a key with formats:write. A Format run's attachments must be JPEG, PNG, WebP, GIF, or AVIF, up to 30 MB each; SVG is not on that list, so export the mark as a PNG first. Put the length, background, and placement in instruction, which wins where it disagrees with the recipe.

• The run answers 202 with a receipt and takes minutes. A completed run's primary_output_url is the one thing to show, on a durable media.sume.com URL that is public to anyone holding it.
• Send an Idempotency-Key: the same key and body return the original run, with no second charge.

curl -sS -X POST "https://api.sume.com/v1/formats/sume/sume-logo-motion-design/runs" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: acme-logo-ident-v1" \
  -d '{
    "instruction": "Short logo ident on a dark background, for the end of our product videos.",
    "attachments": [
      { "type": "input_image", "image_url": "https://example.com/acme-logo.png", "filename": "acme-logo.png" }
    ],
    "generation_spend_cap_usd": 20
  }'

What if the logo is only in a photo?

Remove the background first with RMBG 1.0. POST /v1/rmbg-1.0/remove takes a public HTTPS image_url, and completed results expose PNG artifacts with alpha, mirrored to Sume. Check the cutout, then pass that PNG's media.sume.com URL straight into attachments: a URL already on media.sume.com is not re-copied. The request fields are in Remove background API.

How do I animate the mark myself?

Send POST /v1/videos with the mark as a frame_images entry whose frame_type is first_frame, and describe the move in prompt. On a model whose supported_frame_images lists last_frame, you can also pin the final lockup as the last frame. With model: "sume/auto", create controls default to 720p and 8 seconds, with 3–10 second clips at 16:9 or 9:16. Frame rules are in Image-to-video API: set the first and last frame.

How do I put the logo at the end of a video?

Use Timeline 1.0 (POST /v1/timeline-1.0/render), which returns one MP4, 1080×1920 by default. Add the logo clip as the last video[] slot with a fade or dissolve transition; a transition goes on any slot after the first and lasts at most 1 second and at most half the shorter neighboring slot. The mark's still also works as a slot, since stills are static holds. output.fade_out_seconds (0–5) fades the last seconds to black and silence, and soundtrack.fade_out_seconds (up to 10) fades a music bed.

• Every URL must already be your workspace's media.sume.com artifact or asset. Format run media and generated job outputs are Sume-hosted under media.sume.com; off-host URLs are rejected at admit.
• For a clip from POST /v1/videos, read its media.sume.com artifact URL from GET /v1/jobs/{id}/result. The poll's unsigned_urls point at api.sume.com, not the media host.
• Idempotency-Key is required, and POST /v1/timeline-1.0/plan checks the document without creating a job or reserving credits.
• More transition rules are in Video transitions API.

curl -X POST https://api.sume.com/v1/timeline-1.0/render \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: promo-with-end-card-v1" \
  -d '{
    "audio": { "url": "https://media.sume.com/artifacts/artf_demo/voice.wav", "duration_seconds": 20 },
    "video": [
      { "source_url": "https://media.sume.com/artifacts/artf_demo/promo.mp4", "start": 0, "duration": 16 },
      { "source_url": "https://media.sume.com/artifacts/artf_demo/logo-ident.mp4", "start": 16, "duration": 4,
        "transition": { "type": "fade", "duration": 0.5 } }
    ],
    "output": { "fade_out_seconds": 1 }
  }'

What are the limits?

From the same pages:

• Format: attachments are input_image only, up to 30 MB each and 500 MB per run. A run that cannot finish comes back failed, never a half-finished completed.
• Direct animation: with sume/auto, clips run 3–10 seconds at 16:9 or 9:16. Pinned models list their own resolutions, ratios, and durations in GET /v1/videos/models.
• Timeline: 1–200 slots, each at least 0.2 seconds, and 1–1800 seconds of output. A transition on the first slot is refused (transition_on_first_segment), and so are more than 8 adjacent fades (too_many_chained_transitions).

What does each step cost?

The Format run's full cost, the agent's own LLM turn included, is usage.debited_usd_micros on its receipt.