CLI
Jobs and media inputs
Recover jobs, download artifacts, and register public HTTPS media inputs with the Sume CLI.
Jobs
sume jobs list --agent --json
sume jobs get <job_id> --agent --json
sume jobs status <job_id> --agent --json
sume jobs events <job_id> --agent --json
sume jobs result <job_id> --agent --json
sume jobs watch <job_id>
sume jobs download <job_id> --output-dir ./out
sume jobs cancel <job_id> --confirm-submitIf a process restarts or a local timeout occurs, use the job recovery commands.
Do not submit paid generation again. jobs watch polls until the job gets to a
terminal state or until a timeout occurs. jobs download writes completed
media artifacts into a local directory.
These job helpers work for Avatar CLI submits and for Image/Video/Music jobs that you created through the Developer API.
Assets
If a workflow must use asset ids in place of bare public URLs (or together with them), register or upload first-party input assets:
sume assets list --agent --json
sume assets get <asset_id> --agent --json
sume assets create --source-url https://example.com/reference.png --confirm-submit
sume assets upload-url --content-type image/png --size-bytes 12345 --confirm-submit
sume assets complete <asset_id> --confirm-submit
sume assets download-url <asset_id>
sume assets download <asset_id> --output-dir ./assetsTo examine the exact flags, use sume tools schema assets.create --json and
the related schemas. When the first-party asset lifecycle is not necessary, it
is better to use public HTTPS media URLs in generation payloads.
Use media in Avatar generation
Avatar launch fields such as input.image_url, product_image, and
scene.image_url usually accept public HTTPS URLs. To find the exact
request-body fields, examine these schemas:
sume tools schema avatars.create --json
sume tools schema avatar-videos.create --jsonFor Image/Video/Music media fields, obey the model guides (Image, Video, Music). For the CLI, those families are API-first.