30, 60 and 90-second presenter videos: $5.52, $11.04, $16.56 Standard

A 30-second AI presenter video on Sume costs $5.52 at Standard, $7.35 at Plus and $16.50 at Max; 60 seconds is double that, and 90 seconds is triple. The 90-second video must be two jobs (for example 45 + 45) because one job tops out at 60 seconds.

All three lengths

Rates: Standard $0.184, Plus $0.245, Max $0.55 per second without a product image; $0.194, $0.258, $0.58 with one (Sume pricing page, as of 2026-10-08).

The 90-second case

Both halves must be in the 4 to 60 second window. Reuse the same avatar handle and scene prompt so the join does not change who is on screen. Joining on Timeline 1.0 adds $0.10 per started output minute: a 90-second output is 2 minutes, $0.20.

Reading the table

Cost scales linearly with seconds, so the way to cut a bill is to cut the script, not the number of jobs. Moving from Standard to Plus multiplies the rate by about 1.33 (0.245 / 0.184); Standard to Max by about 2.99 (0.55 / 0.184).

• A product image adds $0.01, $0.013 or $0.03 per second by tier.
• The 4 to 60 second window applies to each job.
• Plan on Plus unless you have a reason: it is the default when quality is omitted.

Practical notes

Quality tiers. quality accepts standard, plus and max. Plus is the default when you omit it. Standard is the fastest Sume execution path, and Max is the highest quality tier with slower turnaround. Because the three differ in both price and speed, decide the tier per stage of your workflow: a quick pass to confirm wording, then a final render once the script is settled.

Output format. Avatar video output is 720p at this time, and the aspect ratio defaults to 9:16 with 1:1, 3:4, 4:3 and 16:9 also accepted. Choose the ratio in the request rather than cropping afterward, since a crop throws away part of a frame you paid for by the second.

Job lifecycle. Every Sume avatar request is job-backed. You submit, store the job id, and poll GET /v1/jobs/{id}/status until it completes, then read GET /v1/jobs/{id}/result. The shared lifecycle also lets you wait with sync or subscribe mode for a limited time instead of polling, and the result carries Sume-hosted artifacts rather than provider URLs, so you never handle a provider queue id. Plan your client around the job, not around a single blocking response.

Idempotency. The docs examples send an Idempotency-Key header on every create call. Use one key per intended job and reuse it only when you retry the same request. A network timeout followed by a fresh submit with a new key is the one path that can create, and bill, a second job. Keep keys human-readable, such as the campaign and scene, so a support lookup is easy.