Video 1.0 last frame: end_image_url needs image_url first

A last-frame request on Video 1.0 must include image_url as well: end_image_url requires image_url (or the deprecated first_frame_url), so you cannot pin only the end of a clip. Send both public HTTPS image URLs.

What modes does Video 1.0 support?

The docs give a goal-to-fields table.

How do I send start and end frames?

Use both fields plus a prompt describing the motion between them.

curl -X POST https://api.sume.com/v1/video-1.0/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: v1-frames-001" \
  -d '{"prompt":"Smooth morph from the empty desk to the finished setup","image_url":"https://example.com/start.png","end_image_url":"https://example.com/end.png","duration":6}'

Which name should I use?

The docs say to prefer image_url over the deprecated first_frame_url and end_image_url over the deprecated last_frame_url.

Do all models accept a last frame?

On the pinned route, supported_frame_images in GET /v1/videos/models says which frame_type values a model takes; see the video docs. Video Router uses end_image_url for the same job; the Video Router docs show the fields.

How do I fetch the finished clip?

Poll GET /v1/jobs/job_123/status until completed, then GET /v1/jobs/job_123/result. The result lists Sume-hosted artifacts with a url and content_type.

Treat artifact URLs as opaque, and do not resubmit a paid request just because a local process timed out. Reuse the job id you stored.