sume models list is a deprecated alias: use sume catalog list
The Sume CLI keeps sume models list as a deprecated alias of sume catalog list. What the catalog command shows, what it cannot do, and how to migrate scripts.

Use sume catalog list. sume models list still works, because the command reference keeps it as a deprecated alias for sume catalog list, but new scripts should call the catalog name and add --json when a program reads the output.
The rename is easy to miss because the old name reads naturally. Anyone who learned the CLI from an older tutorial, a pasted snippet or a generated script will type sume models list first. This post covers what the alias is, what the command does and does not list, and how to move old scripts safely.
What the docs say, read 2026-10-10
The Command reference puts sume catalog list among the read commands and then states the alias in one sentence: sume models list stays as a deprecated alias. The Agent skills page uses only the new name, with --json, in its read-only planning list.
A deprecated alias is a promise of continued behavior for now, not for ever. The page does not give a removal date, so do not assume one. Treat the alias as a migration aid and plan to change callers. The cost of waiting is small today, but a script that fails on a future release is a poor way to learn the alias is gone.
| Command | Status in the docs | Use it for |
|---|---|---|
| sume catalog list | Current | New scripts and interactive use |
| sume catalog list --json | Current, used in agent examples | Programs and agents that parse output |
| sume models list | Deprecated alias for sume catalog list | Old scripts until you migrate them |
| sume tools list --json | Current | Finding CLI tool names and schemas at runtime |
What the catalog command is, and is not
The name matches the API route. The OpenAPI operation behind GET /v1/catalog is listPublicApiCapabilities, so the catalog is a capability listing from the public API, and the command is the terminal view of the same idea.
Because it is a read, it is safe to run on a schedule, for example to log what the account can see before a nightly job starts. Do not read it as a way to generate media. The command reference says plainly that Image, Video and Music generators do not exist as CLI subcommands at this time. To generate those, call the Developer API or use the SDK. The CLI is for account checks, catalog and health reads, jobs, assets and the Avatar commands.
Migrate an old script
The change is a one-word edit, so the risk is in finding every place. Search your repositories, CI files, README snippets and shell aliases. Then decide whether the caller needs structured output.
Keep the change small and verify with a read-only run. Nothing here spends credits, since the listing and doctor commands are reads.
- Search for
models listacross scripts, workflow files and docs you maintain. - Replace it with
catalog list, and add--jsonwhere a program parses the result. - Run
sume doctor --agent --jsonfirst so a missing login fails fast and clearly. - Leave the alias in place only where you cannot redeploy yet, and note it in a comment.
# Old scripts keep working through the deprecated alias
sume models list
# Write new scripts against the current name
sume catalog list --json
# Read-only preflight for an automation run
sume doctor --agent --json
sume tools list --jsonAgents and the read-only habit
The Agent skills page recommends read commands while you plan, and lists the catalog, doctor, tools and jobs reads. Writes need --confirm-submit, and credit-spending Avatar work needs --confirm-paid. A listing never needs either gate.
If an agent runs your old script and gets a deprecation notice or a changed layout, that is the moment to switch to --json, which gives a stable shape to parse. For more on the unattended case, see the CLI in CI and on headless servers and doctor as a CI preflight.
Sources
Related posts
More in Developers
- Sume public_reason: generation_rejected vs temporary error
How Sume picks generation_rejected, temporary_generation_error or generation_failed on a failed job from the provider HTTP status and the retryable flag.
- Sume "Generation could not start": rejected request or outage
Generation could not start is the fallback when a provider rejects a submit. A 4xx gives generation_rejected_request; anything else gives submit_failed.
- Sume image 400 'does not accept aspect_ratio': read supported (Python)
When a Sume image row rejects aspect_ratio with 400 invalid_request, the error carries a supported array. This Python snippet picks the nearest listed ratio.
- How do I ask Sume for 2K? Only 5 of 19 image rows list resolution
Only Nano Banana 2.1, Nano Banana Pro, Imagen 4 Ultra, Ideogram 4.5 and Soul list a resolution field. Send it to FLUX, Seedream or GPT and you get a 400.
Written by Sume