Reference video analysis on Sume: inspect, ingest or video-analyses?

For a reference video, use Sume video inspect for stills and probe, reference ingest for shots and OCR, and note that video-analyses returns 410 on dest.

5 min readSume
All posts

For reference video analysis on Sume, pick by what you need. Use video inspect for a probe, a few stills and an optional transcript. Use reference ingest for shots, on-screen text, audio loudness and cut boundaries from a clip of 300 seconds or less. Do not build on the older POST /v1/video-analyses: it returns 410 video_analysis_retired on dest and stays on prod only until its retirement lands. Sources: Video inspect, Reference ingest and Video analyses, read 2026-10-06.

How do they compare?

Three endpoints, three jobs.

Reference analysis endpoints, read 2026-10-06 from docs.sume.com.
EndpointReturnsLimitPrice
/v1/video-inspectProbe, 8 stills by default, optional STTSource up to 1800 sModal compute; STT $0.01 per audio minute
/v1/reference-ingestShots, OCR text tracks, audio, boundaries, overview stripSource up to 300 sModal compute
/v1/video-analysesLegacy analysisRetiring$0.30 on prod; 410 on dest

What gates reference ingest?

The route sits behind SUME_COM_REFERENCE_INGEST_ENABLED, dest first with a production opt-in, so check that it is on for your environment before you call it. Refusals you can plan for are source_too_long_for_reference_ingest and reference_ingest_stt_required.

Sources

Related posts

More in Media tools

All Media tools posts

Written by Sume