Premiere Pro AI video plugin: what Sume offers instead

Sume's docs describe no Premiere Pro plugin. What they describe is an API: submit one video job per shot, wait for each to finish, and download the MP4 into a folder that Premiere imports. The three requests below are the whole loop, and a webhook can replace the polling.

This page makes no claims about any vendor's Premiere plugin; only Sume's own documented behavior appears here.

Is there a Sume panel inside Premiere?

No such surface appears in the docs. The MCP overview lists hosted MCP, the developer API and CLI, and the Studio Agent product as the surfaces, and https://api.sume.com/v1 is the base for HTTP submits. Anything that runs inside Premiere would be your own script calling that API.

What is the request loop for one shot?

Submit with POST /v1/videos, poll the returned URL, then download when the job is completed. On this route Idempotency-Key is optional, but sending one makes retries safe, and a replay returns the original job.

curl -X POST "https://api.sume.com/v1/videos" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: shot-01" \
  -d '{"model": "seedance-2", "prompt": "Product on a desk, slow push-in"}'

curl "https://api.sume.com/v1/videos/<job_id>" \
  -H "Authorization: Bearer $SUME_API_KEY"

curl "https://api.sume.com/v1/videos/<job_id>/content?index=0" \
  -H "Authorization: Bearer $SUME_API_KEY" --output shot-01.mp4

How do I avoid polling for every shot?

Pass callback_url, which must be HTTPS. Sume POSTs to it once the job reaches a terminal state. The docs' own polling example waits 30 seconds between checks, which is fine for a handful of shots; for a full sequence a webhook receiver is less noisy. A job ends as completed, failed or cancelled, so handle all three.

Can Sume join the shots before Premiere sees them?

Yes, optionally. Timeline 1.0 takes an ordered list of video[] slots plus one audio spine and returns one MP4, at $0.10 per output minute rounded up. It needs media.sume.com sources and an Idempotency-Key. If you would rather cut in Premiere, skip it and import the separate shots. The Timeline docs list the transitions and refusal codes.

How do I check the join before I pay for it?

Call the plan route first. POST /v1/timeline-1.0/plan returns a timeline_plan with duration_seconds, segment_count, billable_minutes and estimated_cost_usd_micros. It creates no job, reserves no credits and downloads no media, and it does not need an Idempotency-Key. A plan cannot predict warnings about short sources being padded or looped, so still read warnings[] on the real render.

What does the join refuse?

Timeline returns stable refusal codes you can match in a script. timeline_must_start_at_zero means the first slot's start was not 0, and transition_on_first_segment means a transition was set on the first slot. Off-host URLs fail with unsupported_media_source, so import each shot before you reference it. A render defaults to mode: "async"; pass mode: "sync" to wait up to 30 seconds for a finished job.