Skip to main content

​
Frequently asked questions

Run the one-line installer for your platform:macOS / Linux:
curl -fsSL https://install.landbase.com | bash
Windows (PowerShell):
irm https://install.landbase.com/windows | iex
After installing, run landbase-cli auth login to authenticate. Full instructions are in the install guide.
Run:
landbase-cli auth login
This opens a browser window. Complete the OAuth login and return to the terminal. The session is saved to ~/.landbase/platform.json.For non-interactive environments (CI, scripts, remote servers), use an API key instead:
landbase-cli auth login --key
Or set the environment variable:
export LANDBASE_API_KEY=lbk_your_key_here
Run the diagnostics command first:
landbase-cli doctor
If your session has expired, re-authenticate:
landbase-cli auth login
For a fresh start, clear all stored credentials and log in again:
landbase-cli auth logout
landbase-cli auth login
See How to troubleshoot authentication for a complete guide.
landbase-cli update
The CLI checks for updates daily and will prompt you when a new version is available. To check manually:
landbase-cli version --check
They enrich different things:
  • enrich — synchronous, single-record lookup for person attributes (title, seniority, department) and company attributes (industry, size, HQ location). Returns immediately.
  • contact-enrich — asynchronous, batch job for finding work email addresses and phone numbers specifically. Returns a request_id you poll for results.
See How enrichment works for a full breakdown.
They describe how confident Landbase is that the candidate returned is the correct match for your input:
  • strong — high confidence, multiple signals align. Use directly.
  • likely — probable match, fewer signals. Good for most tasks.
  • plausible — possible match, some ambiguity. Verify before using in high-stakes situations.
  • unlikely — weak match. Review manually before using.
See Understanding match confidence for a full explanation.
Two common reasons:
  1. The record was not found. If Landbase cannot confidently match your input to a record, it returns nothing rather than potentially incorrect data.
  2. The field is not in Landbase’s database for that record. Not every company or person has every field populated.
Missing fields are not errors. See How enrichment works for more detail.
Pass the extension you want to --download:
landbase-cli "find fintech companies in NYC" --download=results.csv
The CLI runs a publish workflow and downloads the file. This takes about 30–90 seconds. See How to export data in different formats for all format options.
Yes. Install the Landbase Claude Code plugin:
landbase-cli config permissions --yes
Then use slash commands inside Claude Code:
  • /landbase-cli:search — run a prospect search
  • /landbase-cli:auth — check auth status
  • /landbase-cli:setup — verify the installation
See the Using landbase-cli in Claude Code and Codex guide for full details.
Yes. Set your API key as an environment variable and disable interactive features:
export LANDBASE_API_KEY=lbk_your_key
export LANDBASE_NO_UPDATE_CHECK=1
export LANDBASE_NO_TELEMETRY=1
landbase-cli writes JSON to stdout and errors to stderr, with stable exit codes for branching. See How to automate with scripts and CI for a full guide including GitHub Actions examples.
Sessions let you continue a search conversation across multiple commands. Use --session=<label> to assign a label to a research thread:
landbase-cli "find SaaS companies in London" --session=uk-saas
landbase-cli "narrow to 50-200 employees" --session=uk-saas
The second command refines the first instead of starting over. See How sessions work for the full model.
Platform mode (the default) routes through the Landbase cloud gateway and uses OAuth sessions for auth. Legacy mode connects directly to the AgentOS backend using long-lived API keys.Most users should stay on platform mode. Legacy mode exists for backward compatibility with older API keys and integrations. See Platform mode vs. legacy mode.