Video analysis limits: max_scenes 2-40 and the 90 s and 300 s caps

On Sume's video analyses, max_scenes takes 2 to 40 and defaults to 24. A clip longer than about 90 seconds still succeeds but may carry a low_confidence_long_video warning, and a clip past 300 seconds is rejected after the probe. Each accepted analysis reserves and captures $0.30 under the current fixed estimate.

What are the limits?

From the video analyses docs. The route is legacy: create is retired on the dest environment and stays on in production until retirement.

How should I poll?

The docs give a typical runtime of 3-5 minutes and suggest polling every 30-60 seconds, or using jobs_wait over MCP. Read the job envelope in Jobs and results; status and result are separate calls.

curl -X POST https://api.sume.com/v1/video-analyses \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: analysis-limits-001" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/ad.mp4",
    "max_scenes": 12
  }'

How many scenes should I ask for?

The docs give no rule for choosing a value inside 2-40. They do warn that longer videos are less accurate and that short clips give the most reliable results.

Will these limits stay?

The page is marked legacy, so check it before you build on it, and use video inspect for new clip inspection.