Event RSVP clips: invitation, reminder and last call from one avatar
Plan three Sume avatar clips for one event, an 18-second invitation, a 10-second reminder and an 8-second last call. 36 seconds total costs $6.62 on Standard.
An event RSVP sequence is three avatar clips from one presenter: an 18-second invitation, a 10-second reminder and an 8-second last call. That is 36 seconds, which costs $6.62 on Standard, $8.82 on Plus and $19.80 on Max.
Per-second rates are from Sume's public catalog and the avatar video guide, read 2026-10-04. The point is that each clip is its own job, so the reminder can change after the invitation is out without touching the first clip.
Three clips, three jobs
Shorter is better as the date nears: the invitation explains, the reminder confirms, the last call only pushes. All three stay far inside the 4 to 60 second window.
| Clip | Seconds | Standard | Plus | Max |
|---|---|---|---|---|
| Invitation | 18 | $3.31 | $4.41 | $9.90 |
| Reminder | 10 | $1.84 | $2.45 | $5.50 |
| Last call | 8 | $1.47 | $1.96 | $4.40 |
| All three | 36 | $6.62 | $8.82 | $19.80 |
Submit the three in one script
A job per clip, each with its own idempotency key. This stdlib script posts the three requests and prints the job ids; it needs SUME_API_KEY in the environment and a ready avatar handle.
import json, os, urllib.request
KEY = os.environ['SUME_API_KEY']
CLIPS = {
'invite': 'You are invited to our product day on the twentieth. Doors open at ten. Reserve your seat with the link below.',
'reminder': 'Reminder: product day is this Thursday. Your seat is saved.',
'last-call': 'Last call. Seats close tonight.',
}
for name, script in CLIPS.items():
body = json.dumps({'avatar_handle': 'event_host', 'quality': 'standard', 'script': script}).encode()
req = urllib.request.Request(
'https://api.sume.com/v1/avatar-1.0/talking-video', data=body, method='POST',
headers={'Authorization': f'Bearer {KEY}', 'Content-Type': 'application/json',
'Idempotency-Key': f'event-2026-10-{name}'})
with urllib.request.urlopen(req) as r:
print(name, json.load(r).get('request_id'))When the date changes
A spoken date is baked into the render. If the event moves, re-render the clips that mention the date and keep the ones that do not. Write the last call without a date so it survives a small change, and say the weekday plus the date in the reminder.
Disclosure and timing
Send the invitation with a text line saying the host is AI-generated. Say in the clip, the caption or the page around it that the presenter is AI-generated; the API does not add that label for you. Space the three sends by your own calendar; Sume does not schedule delivery.
Sources
Related posts
More in Use cases
- Reels ads: 9:16, sound on, and a safe-zone brief for generated clips
Meta says Reels default to sound on and favours 9:16 video with audio and key messages in the safe zone. A brief for generating clips that follow it.
- Faire product video: three clips, 2 GB, 1080p
Faire's video rules: 1920x1080 or larger, up to 2 GB, up to three videos. How to batch 16:9 product clips on Sume and check each file.
- Food bank volunteer call for Thanksgiving: a 15-second clip, $0.41
Make a silent, captionable volunteer call for a turkey drive before Thursday, November 26, 2026: three stills, a music bed and one Timeline render on Sume.
- Make a for-rent listing video from 8 photos with one Timeline call
A 32-second rental walkthrough from eight listing photos, a music bed and one Sume Timeline render at $0.10 per output minute. Preview with the free plan call.
Written by Sume