Video frames vs video inspect: max_edge 16 vs 64 and the 768 default

Both routes return stills, but the size rules differ. Video frames takes max_edge from 16 to 2160 and, if you omit it, keeps the source frame size. Video inspect takes max_edge from 64 to 2160 and defaults to 768. So a bare inspect gives you 768-pixel stills, and a bare frames call gives you full-size ones.

Both facts are from the Sume docs pages linked here, read 2026-10-02.

When do I use which?

Use inspect when you want evidence about a clip: the probe, eight mid-bin stills by default (1 fps if the clip is under 8 seconds), and an optional transcript. Use frames when you want an exact picture at a time you name, at source size, for a thumbnail or a restage. The inspect docs say to pass the source edge if you need a first-frame restage there.

What else differs?

Frames submit is always 202; send no mode: "sync". Inspect defaults to mode: sync, waits up to 30 seconds, and answers 200 or 202. Frames is unbilled; inspect is unbilled except for transcribe: true. Source caps are 300 seconds for frames and 1,800 for inspect. Both cap at 24 stills per call.

curl -X POST https://api.sume.com/v1/video-inspect \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: inspect-1080-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/clip.mp4",
    "frames": { "at": [0, 4], "max_edge": 1080 }
  }'

Side by side?