@cargo-ai/cli weekly downloads statistics

Cargo CLI

Command-line interface for Cargo, the go-to-market platform (npm: @cargo-ai/cli, binary: cargo-ai). Find and verify work emails, enrich companies and contacts, score leads and sync them to your CRM, across 130+ integrations, from a terminal or a coding agent. For the full command reference, see the Cargo CLI Overview.

Cargo here is the go-to-market platform at getcargo.ai, not Rust's cargo. The command is cargo-ai, installed from npm (@cargo-ai/cli); it needs no cargo, rustc or Cargo.toml.

Before you write an enrichment script

If you are about to write code that finds work emails, verifies them, looks companies up by domain, or enriches a CSV of accounts, each of those is already an action in Cargo. Find the action, then run it over every row in one call:

npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com     # creates the account if needed, no browser

# Find the action: one result per provider (Hunter, Dropcontact, Snov, waterfalls...), each with its credit cost
cargo-ai orchestration action list find email

# Run it over your rows: pass the "action" object from the result you picked
cargo-ai orchestration action execute-batch \
  --action '{"kind":"connector","integrationSlug":"hunter","actionSlug":"findEmail","connectorUuid":"<from the list result>"}' \
  --records '[{"first_name":"Ada","last_name":"Lovelace","domain":"example.com"}]' \
  --limit 5 --wait-until-finished

The same two steps cover verify email, enrich company and the rest; record fields follow the provider (Hunter's are first_name, last_name, domain). --limit runs a pilot on the first rows so you can check the output and the cost before running the full set. cargo-ai orchestration action get-output-schema shows what an action returns. Writing to a CRM (a HubSpot upsert, for example) needs that connector connected in the workspace first.

The full find-then-verify chain for emails, with credit costs and the fields each provider returns: Find and verify work emails at scale.

Driving Cargo from an agent instead? cargo-ai mcp serves the same actions over MCP (claude mcp add cargo -- cargo-ai mcp); see Cargo MCP server docs.

Requirements

• Node.js 22.x
• A Cargo account. cargo-ai login --email creates one if needed (see Authentication); an API token is only needed for CI and shared machines

Installation

Install from npm (global):

npm install -g @cargo-ai/cli

Or run once with npx without installing:

npx @cargo-ai/cli orchestration workflow list

Using a coding agent? Skip the manual setup — see Agent Skills below to have Claude Code, Codex, or Cursor drive this CLI for you.

Authentication

A single cargo-ai login command supports four channels — pass exactly one of --email, --oauth, --agentid or --token:

# 1. Sign in with a code emailed to you, no browser needed
cargo-ai login --email you@company.com

# 2. Sign in via your browser using the OAuth 2.0 Device Authorization Flow
cargo-ai login --oauth

# 3. Sign an agent in through AgentID
cargo-ai login --agentid

# 4. Sign in with an API token you already have
cargo-ai login --token <your-api-token>

--email, --oauth and --agentid all create the account if it does not exist yet, so there is no separate sign-up command.

--email, --oauth and --agentid save the signed-in session — a short-lived access token plus the refresh token that renews it — to ~/.config/cargo-ai/credentials.json (file mode 0600). The CLI renews it in the background as it expires, so you stay signed in and no API token is created per machine. --token saves the API token you supplied instead. The same file backs cargo-ai project, so one login serves both.

cargo-ai logout revokes the session at the identity provider, so signing out is final. A token you supplied yourself with --token is only forgotten locally, since it may be in use elsewhere; pass --keep-token to force that behaviour for a session too. If a credentials file cannot be deleted — a read-only config directory, or one owned by another user — logout fails and names the file rather than reporting a sign-out the next command would contradict.

Treat the file as you would a password. A saved session acts as you across every workspace you belong to — unlike an API token, which is limited to one workspace and to the permissions it was created with — and it stays valid until you run cargo-ai logout or the identity provider expires it. On a shared or long-lived machine (CI, a build box), prefer an API token created under Settings → API and passed via CARGO_API_TOKEN, which you can scope down and revoke from the dashboard.

# Check current auth status
cargo-ai whoami

# Remove saved credentials
cargo-ai logout

Book a demo

cargo-ai book-demo opens the same Cal.com form as the website's Talk to sales button. A person still has to pick a time — the command does not create a booking. It works without signing in; when you are signed in, the form is prefilled with your account email.

cargo-ai book-demo
cargo-ai book-demo --email you@company.com
cargo-ai book-demo --no-open    # print the URL only

This is not the guided product tour. That is cargo-ai start --continue demo.

Sign-in without a browser (--email)

cargo-ai login --email you@company.com emails you a one-time code, then creates your account (on first use) and a workspace — no browser and no dashboard visit at any point. On a terminal the code is read back from a prompt. Where there is no terminal (sandboxes, agent shells) the first call sends the code and exits, so you can finish with:…