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

# Configuration

> Authentication, environment variables, and key resolution for the Reach CLI and MCP server.

## Authentication

Reach requires a Loqate API key for verification. The `parse` command additionally requires an Anthropic API key for Claude Haiku access.

### Loqate API key

Set your API key using any of these methods (listed in resolution order):

| Method               | Example                                                                                                   |
| :------------------- | :-------------------------------------------------------------------------------------------------------- |
| CLI flag             | `lqt verify -k YOUR_KEY -a "..."`                                                                         |
| Environment variable | `export LOQATE_API_KEY=your-key-here` (macOS/Linux) or `$env:LOQATE_API_KEY="your-key-here"` (PowerShell) |
| Key file             | Create a `.loqate-key` file containing just the key                                                       |

<Tip>
  Don't have an API key? [Sign up for a free trial](https://account.loqate.com) with 45 days of access.
</Tip>

### Anthropic API key (parse command only)

Required only for the `parse` command and the `parse_address` MCP tool:

| Method               | Example                                                                                                         |
| :------------------- | :-------------------------------------------------------------------------------------------------------------- |
| CLI flag             | `lqt parse --anthropic-key YOUR_KEY -a "..."`                                                                   |
| Environment variable | `export ANTHROPIC_API_KEY=your-key-here` (macOS/Linux) or `$env:ANTHROPIC_API_KEY="your-key-here"` (PowerShell) |

## Environment variables

| Variable            | Description                                                          |
| :------------------ | :------------------------------------------------------------------- |
| `LOQATE_API_KEY`    | Loqate API key for verification                                      |
| `ANTHROPIC_API_KEY` | Anthropic API key for the `parse` command                            |
| `LOQATE_POLICY`     | Default policy name (`strict`, `shipping`, `standard`, `permissive`) |
| `LOQATE_VERIFY_URL` | Custom verification endpoint URL                                     |
| `LOQATE_VERIFY_KEY` | Custom verification endpoint key                                     |

## Custom endpoints

For customers with a dedicated or on-premise Loqate deployment, override the verification endpoint:

<Tabs>
  <Tab title="macOS / Linux">
    ```bash theme={null}
    export LOQATE_VERIFY_URL=https://your-custom-endpoint.example.com
    export LOQATE_VERIFY_KEY=your-custom-key
    ```
  </Tab>

  <Tab title="Windows (PowerShell)">
    ```powershell theme={null}
    $env:LOQATE_VERIFY_URL="https://your-custom-endpoint.example.com"
    $env:LOQATE_VERIFY_KEY="your-custom-key"
    ```
  </Tab>
</Tabs>

Or via CLI flags:

```bash theme={null}
lqt verify --verify-url https://your-endpoint.example.com --verify-key your-key -a "..."
```

## MCP API key provisioning

When using the remote MCP server, API keys can be provisioned at different levels:

### Organization level

For Claude Desktop, Claude Code, and Cursor, an administrator can set the API key in the organization's project instructions. All team members inherit access automatically.

### User level

Individual users can configure their API key in their client's settings or user preferences.

### Session level

Pass the API key directly in the chat for single-session use. The key is used for that session only and is not stored.

## Costs

* The **CLI and MCP server** are free to use
* **Verification calls** (`verify` command and verification MCP tools) consume credits from your Loqate account
* The **`parse` command** does not consume Loqate credits (it uses Claude Haiku via your Anthropic key)
* No new contract or procurement is required — Reach uses your existing Loqate account