Generation workflows

CLI generation coverage

FamilyCLI submit todayRecommended path
Avatar 1.0sume avatars createCLI or Avatar guide
Avatar Video 1.0sume avatar-videos createCLI or Avatar Video guide
Image 1.0No CLI subcommandDeveloper API
Video 1.0No CLI subcommandDeveloper API
Music 1.0No CLI subcommandDeveloper API

Do not invent Image/Video/Music CLI commands. Call POST /v1/<family>/generate (or the model-run alias) with an Idempotency-Key, then recover the job with sume jobs … if you want CLI polling/download.

Hosted MCP paid tools are also Avatar-focused today — see MCP overview.

Avatar 1.0

The command submits the primary Avatar route POST /v1/avatar-1.0/generate (legacy model-run aliases remain on the API for compatibility). Use --type prompt, --type photo, or --type props; use --payload-json or --payload-file when you need to send an exact request body. Optional --model accepts an exact model-run id when you need that path.

Avatar Video 1.0

The command submits POST /v1/avatar-1.0/talking-video. Read avatar handles with sume avatars list --agent --json or sume avatars get <avatar_id> --agent --json. Avatar-video scripts must estimate to 4-60 seconds inclusive; the CLI validates this before submission.

quality accepts standard, plus, or max. The CLI default when omitted is plus (same as the public API). Use --quality standard for the fastest path, or --quality max when quality matters more than turnaround.

Image, Video, and Music (API-first)

Example Image submit with curl, then CLI job recovery:

Full request fields and constraints:

Recover after submit

All submit commands return or print a job id. Use job commands to recover instead of resubmitting paid work:

Submit commands support exact payloads, idempotency keys, communication modes, webhook URLs, and bounded wait timeouts where the CLI exposes those flags.