Generation workflows
CLI generation coverage
| Family | CLI submit today | Recommended path |
|---|---|---|
| Avatar 1.0 | sume avatars create | CLI or Avatar guide |
| Avatar Video 1.0 | sume avatar-videos create | CLI or Avatar Video guide |
| Image 1.0 | No CLI subcommand | Developer API |
| Video 1.0 | No CLI subcommand | Developer API |
| Music 1.0 | No CLI subcommand | Developer API |
Do not try to use Image/Video/Music CLI commands. These commands do not exist.
Call POST /v1/{image,video,music}-1.0/generate
(or the model-run alias POST /v1/models/sume/<family>-1.0/runs) and send an Idempotency-Key.
If you want the CLI to poll or download the result, use sume jobs … to
recover the job.
Hosted MCP is a different surface. Hosted MCP has generate_image /
generate_video / music_create. The CLI still has no Image/Video/Music
subcommands. Refer to MCP overview.
Avatar 1.0
The command submits the primary Avatar route
POST /v1/avatar-1.0/generate (the API keeps legacy model-run aliases for
compatibility). Use --type prompt, --type photo, or --type props. To send
an exact request body, use --payload-json or --payload-file. The optional
--model flag accepts an exact model-run id when that path is necessary.
Avatar Video 1.0
The command submits POST /v1/avatar-1.0/talking-video. To read avatar
handles, use sume avatars list --agent --json or
sume avatars get <avatar_id> --agent --json.
The estimated length of an avatar-video script must be 4-60 seconds inclusive.
The CLI validates this length before it submits the job.
quality accepts standard, plus, or max. If you do not set it, the CLI
default is plus (the same as the public API). For the fastest path, use
--quality standard. When quality is more important than turnaround, use
--quality max.
Image, Video, and Music (API-first)
This example uses curl to submit an Image job. Then it uses the CLI to recover the job:
Full request fields and constraints:
Recover after submit
All submit commands return or print a job id. To recover, use the job commands. Do not submit paid work again:
Where the CLI exposes those flags, submit commands support exact payloads, idempotency keys, communication modes, webhook URLs, and bounded wait timeouts.