Price plate on 10 product clips for Black Friday: $0.40 total

To put a price plate on ten product clips, trim each clip to the length you want with video trim at $0.02, then overlay a still price-plate image with timeline compose at $0.02. That is $0.04 per SKU and $0.40 for ten, before the Agent turn if one drives the loop.

Black Friday falls on Nov 27, 2026, the day after Thanksgiving on Nov 26. These rates come from the Sume trim and compose pages, read on 2026-10-03. The plate artwork itself is yours; compose only places a still.

Why two jobs per SKU

Compose has two operations, stack and overlay. Overlay lays a still image over a base video using a position, a width_ratio between 0.05 and 1, and a margin_ratio between 0 and 0.45. The image must be a still, and the result is capped at 300 seconds, so trim first only if you want a shorter clip, not because compose requires it.

Trimming is worth the extra $0.02 when raw product clips run long. A shorter base means a smaller output file for every placement, and the plate lands on the part of the clip you chose. Put the plate in the lower third with a margin so the platform's own interface does not cover it.

A price change is a re-run of one step

Because the plate is a separate still, a price correction means a new image and a new compose job for that SKU, $0.02, while the trimmed base clip is reused. Keep one trimmed artifact per SKU for that reason, and name your Idempotency-Key from the SKU and the plate version, such as sku-114-plate-v2, so a retry replays and a new version bills.

If the same clip also needs a spoken or on-screen line, do that with captions first on the trimmed base, then overlay the plate. Compose accepts a video base, so the order is trim, captions, compose.

• Plate position: lower third, margin_ratio 0.08 or more (my choice).
• Plate size: width_ratio near 0.3 for a price tag, larger for a banner (my choice).
• Everything from compose is capped at 300 seconds.

Checking the run

Poll each job's status route and read the result URL when it completes. For a batch of ten, issue the jobs in parallel; each has its own key. Afterwards ask the ledger with GET /v1/usage?job_id= for any job you want to reconcile against the $0.04 per SKU expectation, instead of adding rows yourself.