50-second avatar video with a product image: +$0.50, +$0.65 or +$1.50

On Sume, attaching a product_image to a 50-second avatar video adds $0.50 at Standard, $0.65 at Plus and $1.50 at Max compared with the same clip without one. The with-product totals are $9.70, $12.90 and $29.00.

Both columns for 50 seconds

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).

Where the product image goes

The docs list product_image as optional: omit it for a productless avatar video. Scene direction is separate. You can pass scene as a prompt or as a photo URL, and neither field is described as changing the rate. The pricing page lists only the two columns, no product and with product.

Media fields must be fetchable public HTTPS URLs. Sume rejects localhost and private-network addresses before submitting.

• Per-second surcharge: $0.01 Standard, $0.013 Plus, $0.03 Max.
• Surcharge share of the Plus with-product rate: 0.013 / 0.258 is about 5 percent.
• Surcharge share at Max: 0.03 / 0.58 is about 5 percent too.

When it is worth it

For a pure talking head, skip the image and keep the cheaper column. For a product demo where the item must appear in frame, the surcharge is small relative to the tier rate: on a 50-second Max job it is $1.50 of $29.00. If you are unsure the product will render well, create an avatar video preview first and review the first-frame stills before paying for the full render.

Practical notes

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.

Media inputs. Any media field, whether product_image, scene.image_url or an avatar image_url, must be a fetchable public HTTPS URL. Sume rejects localhost, private-network and non-HTTPS addresses before it submits anything, so a broken link fails fast instead of consuming a render. Host reference images where Sume can fetch them and keep them available until the job finishes.

Reading results. A completed result can include public media.sume.com video artifacts, and for avatar videos also public-safe preview fields such as preview_image_url and scene_previews. You can list or read finished videos with GET /v1/avatar-videos and GET /v1/avatar-videos/{id}. Store the job id and the video id together so a billing line can be traced back to a creative.

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.