Verify Command

The verify command validates contact data against Loqate APIs and returns a confidence score, match-level data, and a policy-aware recommendation.

Usage

lqt verify [flags]

Flags

Flag	Description
`-a, --address`	Full address string
`-e, --email`	Email address
`-p, --phone`	Phone number (E.164 format recommended)
`-c, --country`	ISO 2-letter country code
`--policy`	Policy to apply: `strict`, `shipping`, `standard`, `permissive`
`--policy-file`	Path to a custom policy JSON file
`-b, --batch`	Path to a CSV/TSV file for batch processing
`-o, --output`	Output format: `json`, `jsonl`, or `table`
`-k, --key`	Override the Loqate API key
`--field`	Pass extended Loqate input fields
`--option`	Pass additional API options
`--summary`	Display summary statistics (batch mode)

Examples

Verify an address

lqt verify -a "10 Downing Street, London, SW1A 2AA, GB" -o json

Verify with a specific policy

lqt verify -a "10 Downing St, London, GB" --policy shipping -o json

Verify address, email, and phone together

lqt verify \
  -a "221B Baker St, London, GB" \
  -e "sherlock@example.com" \
  -p "+442071234567" \
  --policy strict \
  -o json

Human-readable table output

lqt verify -a "125 Summer St, Boston, MA 02110, US" -o table

Response fields

Address

Field	Description
`confidence`	Score between 0 and 1
`recommendation`	`accept`, `review`, or `reject` based on the active policy
`avc`	Address Verification Code (e.g., `V44-I44-P7-100`)
`verification_status`	`V` (verified), `P` (partially verified), `U` (unverified), `R` (reverified)
`match_level`	`premise`, `street`, `locality`, `administrative_area`, or `country`

Email

Field	Description
`confidence`	Score between 0 and 1
`recommendation`	`accept`, `review`, or `reject`
`response_code`	Loqate email validation response
`risk`	`low`, `medium`, or `high`
`flags`	Array of risk indicators (e.g., `disposable_domain`)

Phone

Field	Description
`confidence`	Score between 0 and 1
`recommendation`	`accept`, `review`, or `reject`
`verified`	Whether the phone number is valid
`number_type`	`mobile`, `landline`, `voip`, etc.

Overall

Field	Description
`recommendation`	Lowest-confidence field’s recommendation
`confidence`	Lowest confidence score across all verified fields
`policy`	Name of the policy that was applied

Exit codes

The CLI returns exit codes that agents and scripts can use for control flow:

Code	Meaning
`0`	`ACCEPT` — all fields passed the policy threshold
`1`	`REVIEW` — one or more fields need human review
`2`	`REJECT` — one or more fields failed the policy threshold
`3`	`ERROR` — a request or configuration error occurred

Getting Started

Reach CLI

MCP Server

IBM watsonx Orchestrate

Reference

Usage

Flags

Examples

Verify an address

Verify with a specific policy

Verify address, email, and phone together

Human-readable table output

Response fields

Address

Email

Phone

Overall

Exit codes

​Usage

​Flags

​Examples

​Verify an address

​Verify with a specific policy

​Verify address, email, and phone together

​Human-readable table output

​Response fields

​Address

​Email

​Phone

​Overall

​Exit codes

Usage

Flags

Examples

Verify an address

Verify with a specific policy

Verify address, email, and phone together

Human-readable table output

Response fields

Address

Email

Phone

Overall

Exit codes