50 face-swap ad variants: $138.00 at standard, $412.50 at max

Fifty Avatar Face Swap beta jobs reserve $138.00 at the standard tier (50 x $2.76), $183.75 at plus (50 x $3.675) and $412.50 at max (50 x $8.25) on Sume. The catalog says each job reserves the Avatar Video price for the maximum beta source-video duration, which is 15 seconds, and that final workflow pricing may be refined before general availability.

Per-second tiers and the 15-second reservation

The per-second rates are $0.184 for standard, $0.245 for plus and $0.55 for max. Fifteen seconds of each gives $2.76, $3.675 and $8.25. The catalog lists the same figure as the estimate, the minimum and the maximum for each tier, which tells you that the reservation does not depend on the length of your clip. Whether a shorter clip is captured at a lower amount is not stated in the docs, so budget with the reservation.

What a variant batch needs

Each job takes a ready avatar handle, a public HTTPS source video of roughly 4 to 15 seconds with usable audio, and a quality value. The quality field is required and has no default. Signed or private URLs, localhost and non-HTTPS links are refused.

Keeping the balance honest

Reservations hold money until the job completes, so a batch of 50 at max holds up to $412.50 at once if all are in flight. Submit in waves of ten, which holds $82.50 at max, and wait for results before the next wave. Use webhooks rather than polling, and check the Errors and credits page for how failed jobs return their reservation.

A wave plan

Fifty jobs in five waves of ten at standard reserve $27.60 at a time (10 x $2.76). Wave one tells you if the avatar and source clips work. Fix problems before wave two, since a systematic error repeated fifty times costs $138.00.

Tier choice: standard costs $0.184 per second, plus $0.245 (33 percent more) and max $0.55 (about three times standard). The docs do not describe how the tiers differ visually, so test a single clip at each tier before you pick: 3 jobs x $2.76, $3.675 and $8.25 is $14.685.

Webhooks save polling. Use the Jobs and results page for the job states, and treat resource_status as the readiness signal.