The parse command standardizes contact data using Claude Haiku. It splits unstructured addresses into components, normalizes phone numbers, and validates email format — without making Loqate API calls or consuming credits.
Usage
Flags
| Flag | Description |
|---|
-a, --address | Address to parse into components |
-e, --email | Email to validate format |
-p, --phone | Phone number to normalize |
-c, --country | Country hint (ISO 2-letter code) |
-b, --batch | Path to a CSV/TSV file for batch parsing |
-o, --output | Output format: json, jsonl, or table |
--anthropic-key | Override the Anthropic API key |
Examples
Parse an address
lqt parse -a "221B Baker Street London NW1 6XE United Kingdom"
Parse with a country hint
lqt parse -a "125 Summer St Boston MA 02110" -c US -o json
Batch parsing
lqt parse -b addresses.csv -o jsonl
Requirements
The parse command requires an Anthropic API key for Claude Haiku access:
macOS / Linux
Windows (PowerShell)
export ANTHROPIC_API_KEY=your-key-here
$env:ANTHROPIC_API_KEY="your-key-here"
The parse command does not call Loqate APIs and does not consume any Loqate account credits. It uses Claude Haiku for address standardization only.
When to use parse vs verify
| Use case | Command |
|---|
| Standardize address format before storage | parse |
| Split unstructured address into components | parse |
| Confirm an address is real and deliverable | verify |
| Get a confidence score and recommendation | verify |
| Pre-process data before batch verification | parse, then verify |
