The network, from your terminal.
Manage projects, deployments and your account without leaving the shell. Authenticate once, then script escrow, tasks and payouts into your CI - the same API, made for automation.
Get going in three commands.
Install
Pull the CLI from npm or the install script. One binary, no runtime to babysit.
Log in
Run ivo login to authenticate, or set an API key env var for headless and CI use.
Do work
ivo projects list, ivo escrow fund, ivo deploy - the network is now a command away.
What you can drive from the shell.
The everyday actions you would click through - now scriptable and repeatable.
Projects & tasks
Create, list and update projects and tasks. Pipe output as JSON straight into other tools.
Deployments
Ship and roll back from the terminal, so releases live in your scripts, not a dashboard.
Account & keys
Manage profile, API keys and scopes without opening a browser.
Escrow & payouts
Fund escrow and trigger payouts from automation - idempotent, so retries stay safe.
JSON output
Add --json to any command for clean, parseable output ready for jq and pipelines.
Profiles
Switch between accounts and environments with named profiles - test and live, side by side.
Where the CLI earns its keep.
Automation and reproducibility, without a UI in the loop.
Headless by design
Authenticate with an API key env var and run any command in CI. Gate deploys on escrow state, post tasks on merge, automate the busywork.
Wire up CIFaster than clicking
Batch updates, scripted reports and one-liners over the whole network. Everything the dashboard does, in muscle memory.
Why use the CLI.
Same network, made for automation.
Reproducible
Commands live in scripts and version control - your workflow is auditable and repeatable.
Fast
No page loads. Tab-complete commands and get answers in milliseconds.
Secure
Scoped keys and env-var auth keep secrets out of your shell history and your code.
Versioned
The CLI tracks /api/v2 and ships with semantic versioning - upgrades are predictable.
CLI questions.
How do I authenticate in CI?
Set an API key as an environment variable and the CLI uses it automatically - no interactive login. Use a scoped key so the pipeline can only touch what it needs.
Can I get machine-readable output?
Yes. Add --json to any command for structured output you can pipe into jq or other tools, instead of formatted tables.
Does it do everything the API does?
It covers the common workflows - projects, tasks, deployments, escrow, payouts and account management. For anything bespoke, the CLI and the REST API share the same backend.
How do I manage multiple accounts?
Use named profiles to switch between accounts and between test and live environments without re-authenticating each time.
Bring the network into your shell.
Install the CLI, log in once and script escrow, tasks and deployments into your pipelines.