CLI reference

The lorivo CLI validates, uploads, and deploys LoRA adapters. Install it from the Quickstart or with curl -fsSL https://lorivo.dev/install.sh | sh.

Commands

Command	Description
`login <api-key>`	Save your API key (the control-plane URL is built in)
`deploy <dir> [options]`	Validate, upload and deploy an adapter
`list`	List adapters and their deploy status
`rollback <name>`	Roll back an adapter to a previous version
`keys <command>`	Manage inference API keys

Configuration

lorivo login stores { apiUrl, adminKey } in ~/.adapters/config.json (written with mode 0600). The control-plane URL is built into the CLI (https://lorivo.dev) and environment variables override the saved file, so CI and scripts can skip login entirely.

~/.adapters/config.json

{
  "apiUrl": "https://lorivo.dev",
  "adminKey": "ad_…"
}

Variable	Default	Purpose
`ADAPTERS_API_URL`	`https://lorivo.dev`	Control-plane base URL (overrides saved config)
`ADAPTERS_ADMIN_KEY`	-	API key used for all requests (overrides saved config)
`ADAPTERS_API_KEY`	-	Alias of `ADAPTERS_ADMIN_KEY`
`ADAPTERS_CONFIG`	`~/.adapters/config.json`	Path to the config file
`ADAPTERS_DEFAULT_BASE`	`qwen3-4b`	Default `--base` for `deploy`
`ADAPTERS_TIMEOUT_MS`	`300000`	Request timeout in milliseconds
`ADAPTERS_VERSION`	built-in	Overrides the version reported by `--version`

Key scopes

Two kinds of keys work with the CLI:

Admin key: full platform access over every org and adapter. Can target orgs with --org and mint keys for any org.
Org key (ad_…) is scoped to one org. --org and keys create <org> are ignored; the key always acts on its own org.

Org keys are the same keys used for inference. One key covers both /v1/* calls and CLI management.

Global options

lorivo --version
lorivo --help
lorivo <command> --help