> ## Documentation Index
> Fetch the complete documentation index at: https://www.landbase.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Answers to common questions about landbase-cli installation, authentication, data, rate limits, and platform behavior.

# Frequently asked questions

<AccordionGroup>
  <Accordion title="How do I install landbase-cli?">
    Run the one-line installer for your platform:

    **macOS / Linux:**

    ```bash theme={null}
    curl -fsSL https://install.landbase.com | bash
    ```

    **Windows (PowerShell):**

    ```powershell theme={null}
    irm https://install.landbase.com/windows | iex
    ```

    After installing, run `landbase-cli auth login` to authenticate. Full instructions are in the [install guide](/docs/install).
  </Accordion>

  <Accordion title="How do I authenticate?">
    Run:

    ```bash theme={null}
    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:

    ```bash theme={null}
    landbase-cli auth login --key
    ```

    Or set the environment variable:

    ```bash theme={null}
    export LANDBASE_API_KEY=lbk_your_key_here
    ```
  </Accordion>

  <Accordion title="My authentication stopped working. What do I do?">
    Run the diagnostics command first:

    ```bash theme={null}
    landbase-cli doctor
    ```

    If your session has expired, re-authenticate:

    ```bash theme={null}
    landbase-cli auth login
    ```

    For a fresh start, clear all stored credentials and log in again:

    ```bash theme={null}
    landbase-cli auth logout
    landbase-cli auth login
    ```

    See [How to troubleshoot authentication](/docs/how-to/troubleshoot-auth) for a complete guide.
  </Accordion>

  <Accordion title="How do I update landbase-cli to the latest version?">
    ```bash theme={null}
    landbase-cli update
    ```

    The CLI checks for updates daily and will prompt you when a new version is available. To check manually:

    ```bash theme={null}
    landbase-cli version --check
    ```
  </Accordion>

  <Accordion title="What is the difference between enrich and contact-enrich?">
    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](/docs/explanation/how-enrichment-works) for a full breakdown.
  </Accordion>

  <Accordion title="What do the match confidence tiers (strong, likely, plausible, unlikely) mean?">
    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](/docs/explanation/match-confidence) for a full explanation.
  </Accordion>

  <Accordion title="Why are some fields missing from enrichment results?">
    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](/docs/explanation/how-enrichment-works) for more detail.
  </Accordion>

  <Accordion title="How do I download results as CSV instead of JSONL?">
    Pass the extension you want to `--download`:

    ```bash theme={null}
    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](/docs/how-to/export-data-formats) for all format options.
  </Accordion>

  <Accordion title="Can I use landbase-cli in Claude Code?">
    Yes. Install the Landbase Claude Code plugin:

    ```bash theme={null}
    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](/docs/landbase-cli) guide for full details.
  </Accordion>

  <Accordion title="Can I use landbase-cli in a script or CI pipeline?">
    Yes. Set your API key as an environment variable and disable interactive features:

    ```bash theme={null}
    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](/docs/how-to/automate-with-scripts) for a full guide including GitHub Actions examples.
  </Accordion>

  <Accordion title="What are sessions and when should I use them?">
    Sessions let you continue a search conversation across multiple commands. Use `--session=<label>` to assign a label to a research thread:

    ```bash theme={null}
    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](/docs/explanation/how-sessions-work) for the full model.
  </Accordion>

  <Accordion title="What is platform mode and what is legacy mode?">
    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](/docs/explanation/platform-vs-legacy).
  </Accordion>

  <Accordion title="How do I get support?">
    * Run `landbase-cli doctor` for self-diagnosis
    * Visit [support.landbase.com](https://support.landbase.com/landbase/directories)
    * For bugs or feature requests in the CLI itself, open an issue on the [landbase-cli GitHub repository](https://github.com/landbaseapp/landbase-cli)
  </Accordion>
</AccordionGroup>