Skip to main content

​
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):
Don’t have an API key? Sign up for a free trial with 45 days of access.

​
Anthropic API key (parse command only)

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

​
Environment variables

​
Custom endpoints

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

​
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