Skip to main content
These commands are available in Prime CLI 0.21.0 and later. Deploy a dedicated endpoint provides a walkthrough. Deployment management uses the platform API and requires Model Factory permissions, factory:read for reads and factory:write for mutations. Model requests use the inference API and require Inference permission.

Commands

All deployment commands accept --output json, abbreviated -o json. The default is human-readable output. prime train checkpoints <run-id> --status READY lists saved checkpoints.

Catalog and catalog deployment options

The deployment argument is the catalog’s id, not its repo, slug, or display name. prime inference models lists models for requests to shared inference. prime inference catalog lists configurations for dedicated deployments.

Checkpoint deployment options

Both checkpoint command names have these options. Neither accepts --cluster, --name, or --replicas. Placement defaults to the run’s own team cluster when it still belongs to that team, and to on-demand capacity otherwise. The deployment API also accepts explicit on-demand placement and initial replica count.

Lifecycle options

get, scale, and delete address the deployment by ID and have no --team option. The API checks access to the deployment’s account.

JSON output

catalog -o json returns {models: [...], clusters: [...]}. deployments list -o json returns {data: [...]}. Other deployment commands return a deployment object. In JSON mode, deployment wait progress and errors go to stderr. Stdout contains the JSON result when one is returned.

Wait and deletion behavior

--wait exits successfully when the deployment is RUNNING. A terminal deployment state, timeout, or repeated polling failure exits with code 1. A timeout or lost API connection does not delete the deployment. Scaling and deletion are asynchronous. A scale response acknowledges the desired count. Deletion returns the deployment in TERMINATING state while teardown proceeds. Once teardown removes the record, get can return not found.