The CLI gives you the same data and agent from your terminal, which is where repeatable and large-scale work belongs. This page takes you from nothing installed to a verified setup: install, sign in, claim your credits, connect your CRM, and run a quick check before you spend anything.
Installing the CLI takes one command. Pick the line for your operating system.
curl -fsSL https://cli.landbase.com/install.sh | bash$ProgressPreference = 'SilentlyContinue'; irm https://cli.landbase.com/install.ps1 | iexConfirm it worked by checking the version. If you see a version number you are installed. If the terminal cannot find landbase-cli right afterward, it is almost always a PATH issue, which is a quick fix.
landbase-cli --versionBefore the CLI can pull data, you sign in through a browser-based consent flow, so you never paste a password into the terminal.
landbase-cli auth loginThis opens your browser. Approve the consent screen and the CLI is signed in. Use the same account you use for the web app, so your sessions, datasets, and credits all live in one place. You sign in once, and the CLI remembers you until you log out.
New accounts get 1,000 credits free on signup, worth $49, with no card required and no expiry. Activate them, then read your balance so you know what each action costs. Most of what you do is free, and you are only charged for verified enrichment, where an email costs 1 credit and a phone number costs 10.
You can connect your CRM from the CLI so Landbase works directly with the records you already have. Connecting HubSpot or Salesforce lets Landbase compare against and add to your existing records instead of copy-pasting between tools. Read access lets Landbase see your records, and write access lets it add to them. This is a CLI capability today, since the web app cannot connect a CRM yet.
Before you rely on the CLI, run two quick, read-only commands that confirm install, auth, and access. They change nothing and spend no credits.
landbase-cli --version
landbase-cli auth statusThe version command confirms the CLI is installed and on your PATH, and auth status confirms you are signed in. Run them any time something feels off.