Realtor open-house reminders: 20 avatar clips, cost and queue by plan

Twenty 15-second open-house avatar clips cost $55.20 on Sume's standard tier. A Free workspace accepts 6 jobs at once and Pro accepts 24, so plan the submit.

5 min readSume
All posts

A brokerage that sends a 15-second avatar reminder for each of 20 open houses spends $55.20 on Sume's standard tier, $73.50 on plus and $165.00 on max at list rates with no product image. The cost is the easy part. A Free workspace accepts six paid jobs at a time and a Pro workspace accepts 24, so 20 reminders submitted together need Pro or a second wave.

Rates are from Sume API pricing, the route from Generate avatar video and the limits from Generation admission, all read 2026-10-03.

What does each listing clip cost?

Each reminder is one job of about 15 seconds, within the 4 to 60 second window. The listing photo can go in as a scene of type photo, which sets the setting without a product image, so the productless rate applies. If you do attach a product_image, the higher with-product rate applies instead.

20 open-house reminders of 15 seconds each (read 2026-10-03)
TierPer clip20 clipsNotes
standard$2.76$55.20Fastest Sume execution path
plus$3.675$73.50Default when quality is omitted
max$8.25$165.00Highest quality; slower turnaround

Will 20 jobs be accepted?

Generation concurrency is plan-based: 1 on Free, 4 on Pro, 8 on Startup, 20 on Scale and Enterprise. Queue capacity defaults to the larger of 3 and five times the concurrency, which makes accepted capacity 6, 24, 48 and 120. A submit beyond accepted capacity fails with 429 queue_full, and the docs say to wait for jobs to finish or cancel queued ones and retry with the same idempotency key.

So 20 reminders fit in one submission on Pro, Startup and above, and on Free you submit six, wait, and submit the next six, four waves in all. The submit response includes generation_limits with wave_size_hint, which is max(1, floor(queue_capacity_remaining * 0.75)), so a fresh Pro workspace gets a hint of 18. The docs say the hint is a submission-wave hint only and not a concurrency limit.

Accepted jobs by plan (read 2026-10-03)
PlanProcessing concurrencyAccepted job capacity20 reminders in one go?
Free16No: four waves (6, 6, 6, 2)
Pro424Yes
Startup848Yes
Scale20120Yes

A workable routine

Write one script template with the address, date and time as variables, and keep the agent's name and the call to action fixed so the clips look like a series. Derive each job's Idempotency-Key from the listing id and the open-house date, so a retry after a 429 cannot make a second paid clip for the same house.

Preview the first frame of one listing before you submit the other 19. A preview shows the composition without a full render, and the final tier can be chosen when you call generate-video on it, with no new preview needed for a tier change. The cost tables price final renders only; the docs do not give a separate preview price, so check it before previewing every listing.

  • Keep the date in the script as words, since it is read aloud.
  • Re-render only the listing whose time changed, at the cost of one clip.
  • Check fair-housing and brokerage rules for what a script may say before it is rendered; Sume does not review script claims.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume