@vruum/cli

vruum

The headless CLI for the Vruum revenue platform — the universal floor for every agent harness. Drive your pipeline, deals, outreach, marketing, and knowledge base from the terminal or from any automation, with machine-stable --json output on every command.

vruum deal list --json | jq '.[] | select(.stage == "negotiation")'

Install

npm (requires Node ≥ 22)

npm install -g @vruum/cli
# or run without installing:
npx @vruum/cli --help

Homebrew (macOS / Linux)

brew tap vruum-gtm/vruum
brew install vruum

install script (standalone binary — no Node required)

curl -fsSL https://vruum.ai/install.sh | sh

The script detects your OS/arch, downloads the matching prebuilt binary from the latest GitHub release, verifies its SHA-256 checksum, and installs it to /usr/local/bin (falling back to ~/.local/bin). Re-running upgrades in place.

Prebuilt binaries are published for darwin-arm64, darwin-x64, linux-arm64, and linux-x64.

Authentication

vruum authenticates with a personal access token (PAT, vk_live_…). Generate one in the Vruum web app under Settings → API tokens.

# Interactive: prompts for the token (input hidden) and stores it in ~/.vruum
vruum login

# Non-interactive: pass it explicitly or pipe it in
vruum login --token vk_live_xxx
echo "vk_live_xxx" | vruum login

# Confirm who you are authenticated as
vruum whoami

# Remove stored credentials
vruum logout

Environment variables

Variable	Purpose
VRUUM_TOKEN	PAT to use (overrides the stored credentials file)
VRUUM_API_URL	Override the API base URL (default https://api.vruum.ai)
VRUUM_CONFIG_DIR	Override the config/credentials directory (default ~/.vruum)

VRUUM_TOKEN makes the CLI fully stateless — ideal for CI and agent harnesses:

VRUUM_TOKEN=vk_live_xxx vruum deal list --json

Operating on behalf of a company (operators)

Operators managing multiple tenants can scope any command to a company with the global --for-company flag:

vruum --for-company <company_id> deal list

Global flags

Flag	Description
--json	Emit machine-stable JSON instead of a table
--for-company <id>	Act on behalf of a company (operator multi-tenant)
--api-url <url>	Override the API base URL for this invocation
-V, --version	Print the version
-h, --help	Show help for any command or subcommand

Command tree

Run vruum <group> --help for the flags of any subcommand.

Group	Subcommands
account	get · set-stage · set-state · note
ad	list · create · approve · reject · pause · resume · budget
campaign	list · get · create · update · clone · delete · members
company	list · get · create · update
content	list · create · edit · schedule · publish · delete
cta	list · create · update · delete · set-default
deal	list · get · create · update · stage · won · lost · reopen · stakeholder
engagement	queue · approve · edit · skip
kb	list · show · upsert · reindex · delete
message	queue · approve · reject · edit · regenerate · bulk-approve · bulk-reject · bulk-edit
people	list · get · create · update · archive · note · import
plan	get · start · pause · resume · stop · touch · override · channels
proposal	list · get · create · draft · send · cancel
review	outreach · deals · engagement · content
settings	get · set
skills	list · show
task	list · create · complete · delete
auth	login · logout · whoami

--json examples

Every command supports --json for stable, scriptable output:

# Pipe deals through jq
vruum deal list --json | jq '.[] | {name, stage, amount}'

# Triage the outreach queue in a script
vruum review outreach --json | jq '.items | length'

# Approve every pending message non-interactively
vruum message queue --json | jq -r '.[].id' | xargs -I{} vruum message approve {}

# Snapshot the engagement queue for an agent
VRUUM_TOKEN=vk_live_xxx vruum engagement queue --json

Without --json, commands print human-readable tables; with it, they print JSON suitable for jq, agents, and CI.

License

MIT