Sume CLI avatar-videos batch: plan, create, watch, result
The Sume CLI batches avatar videos in four steps against local state files. What each step does, and why the per-item idempotency key makes reruns safe.
The four steps
The CLI docs describe batch helpers under both sume avatars batch and sume avatar-videos batch. They work in four steps against local state files: plan, create, watch and result.
| Step | What it does | Network spend? |
|---|---|---|
| plan | Builds the batch locally from your items | No, local |
| create | Submits each item with its own stable idempotency key | Yes, paid |
| watch | Follows the submitted jobs until they end | No new spend |
| result | Collects finished output from the state file | No |
Why local state matters
Each item keeps a stable idempotency key in the state file. If your terminal dies halfway, running create again resends the same keys, so items already accepted are not billed twice. Combined with the 429 queue_full rule, a rerun after capacity opens is safe.
Read the exact flags
sume avatar-videos batch --help
sume avatars batch --helpBudget first
Plan is local, so cost it by hand before create. Forty 30 s plus clips are 1,200 s at $0.245, which is $294. At standard the same batch is $220.80.
Limits that still apply
- Each clip must estimate at 4 to 60 s.
- Your plan concurrency caps how many run at once: Pro 4 with 20 queued, Scale 20 with 100.
- Paid CLI avatar creation needs an explicit confirm flag, as the docs describe.
Sources
Related posts
More in Developers
- Sume CLI quickstart: create an avatar video, follow it with jobs
Install the Sume CLI, log in, create a paid avatar video, and follow the job with sume jobs status, result and events. Why Image and Video have no CLI command.
- Map the Sume error envelope to RFC 9457 problem details in 15 lines
RFC 9457 defines type, status, title, detail and instance. Sume's error.code, message and request_id map onto them; keep the retry fields as extensions.
- Format run stuck queued? Sume waiting vs runtime_unavailable
A queued Sume Format run reports queue.state waiting or runtime_unavailable, with position always null. A bash and jq check that reads the status route.
- Sume job webhooks are terminal-only: drive a queue from three events
Sume sends job.completed, job.failed and job.canceled only, with no progress events. Publish on completed, alert on failed, and poll events for progress.
Written by Sume