[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_103":104},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module '@gbgplc/lqt' is not configured","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":26,"_34":-5,"_35":36,"_37":-5,"_38":-5,"_39":40,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_55":48,"_56":57,"_58":59,"_60":-5,"_61":-5,"_62":-5,"_63":-5,"_64":65,"_66":67,"_68":69,"_70":71,"_72":73,"_74":-5,"_75":-5,"_76":-5,"_77":48,"_78":-5,"_79":80,"_81":82,"_83":84,"_85":86,"_87":88,"_89":90,"_91":92},"apiUrl","https://odel.app/api","creator","gbgplc","moduleId","lqt","@gbgplc/lqt","displayName","GBG Loqate - Reach","tagline","Verify addresses, email addresses, and phone numbers with confidence scores.","iconKey","https://avatars.githubusercontent.com/u/35372963?v=4","category","communication","status","published","metaDescription","metaKeywords","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://reach.prod.fabric.gbgplatforms.com/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1781363432000,"updatedAt",1781499638000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.gbgplc%2Flqt","sourceVerified",true,"importedAt","upstreamStars",2,"upstreamUpdatedAt",1779883040000,"detectedTransport","detectedAuthType","probeStatus","lastProbedAt","githubRepoUrl","https://github.com/gbgplc/lqt","githubRepoFullName","gbgplc/lqt","releaseId","ext-gbgplc-lqt","version","0.6.2","descriptionMarkdown","

\n $\"Loqate$ \n

\n\n

Loqate CLI

\n\n

\n Verify addresses, emails, and phone numbers against Loqate's APIs.
\n Get confidence scores, policy-aware recommendations, and full auditability — in one command.
\n Real-time verification decisioning for agents that need to know whether contact data is good enough for the job.
\n Part of GBG Reach.\n

\n\n

\n lqt verify · lqt parse · lqt mcp\n

\n\n---\n\n## Install\n\n### macOS\n\n```bash\n# Apple Silicon (M1/M2/M3/M4)\ncurl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_darwin_arm64.tar.gz | tar xz\nsudo mv lqt /usr/local/bin/\n\n# Intel\ncurl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_darwin_amd64.tar.gz | tar xz\nsudo mv lqt /usr/local/bin/\n```\n\n### Linux\n\n```bash\n# x86_64\ncurl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_linux_amd64.tar.gz | tar xz\nsudo mv lqt /usr/local/bin/\n\n# ARM64\ncurl -sL https://github.com/gbgplc/lqt/releases/latest/download/lqt_linux_arm64.tar.gz | tar xz\nsudo mv lqt /usr/local/bin/\n```\n\n### Windows\n\n1. Download `lqt_windows_amd64.zip` from the [latest release](https://github.com/gbgplc/lqt/releases/latest)\n2. Extract `lqt.exe`\n3. Move it to a directory on your `PATH`, or run it directly\n\n### Verify Installation\n\n```bash\nlqt version\n```\n\n### All Downloads\n\nSee [Releases](https://github.com/gbgplc/lqt/releases) for all versions and platforms. Each release includes SHA-256 checksums.\n\n| Platform | Archive |\n|----------|---------|\n| macOS (Apple Silicon) | `lqt_*_darwin_arm64.tar.gz` |\n| macOS (Intel) | `lqt_*_darwin_amd64.tar.gz` |\n| Linux (x86_64) | `lqt_*_linux_amd64.tar.gz` |\n| Linux (ARM64) | `lqt_*_linux_arm64.tar.gz` |\n| Windows (x86_64) | `lqt_*_windows_amd64.zip` |\n\n---\n\n## Quick Start\n\n### API Keys\n\nYou need a **Loqate API key** for verification. Optionally, an **Anthropic API key** for the `parse` command.\n\n**macOS / Linux:**\n```bash\nexport LOQATE_API_KEY=your-key-here\n\n# Optional — for lqt parse\nexport ANTHROPIC_API_KEY=your-key-here\n```\n\n**Windows (PowerShell):**\n```powershell\n$env:LOQATE_API_KEY=\"your-key-here\"\n\n# Optional — for lqt parse\n$env:ANTHROPIC_API_KEY=\"your-key-here\"\n```\n\n### Your First Verification\n\n**macOS / Linux:**\n```bash\n# Verify an address\nlqt verify --address \"125 Summer Street, Boston, MA 02110, US\"\n\n# Verify address + email + phone with a policy\nlqt verify -a \"10 Downing St, London, GB\" \\\n -e \"pm@gov.uk\" \\\n -p \"+442071234567\" \\\n --policy shipping\n\n# Parse and standardize without calling Loqate (uses Claude)\nlqt parse --address \"125 summer street boston ma 02110 us\"\n```\n\n**Windows (PowerShell):**\n```powershell\n# Verify an address\n.\\lqt.exe verify --address \"125 Summer Street, Boston, MA 02110, US\"\n\n# Verify address + email + phone with a policy\n.\\lqt.exe verify -a \"10 Downing St, London, GB\" -e \"pm@gov.uk\" -p \"+442071234567\" --policy shipping\n\n# Parse and standardize without calling Loqate (uses Claude)\n.\\lqt.exe parse --address \"125 summer street boston ma 02110 us\"\n```\n\n---\n\n## Commands\n\n### verify\n\nVerify addresses, emails, and/or phone numbers against Loqate's APIs. Returns a confidence score and a policy-driven recommendation (accept, review, or reject).\n\n```bash\nlqt verify [flags]\n```\n\n**Flags:**\n\n| Flag | Short | Description |\n|------|-------|-------------|\n| `--address` | `-a` | Full address to verify |\n| `--locality` | | City/town |\n| `--admin-area` | | State/province |\n| `--postcode` | | Postal/ZIP code |\n| `--country` | `-c` | ISO 2-letter country code |\n| `--email` | `-e` | Email address to verify |\n| `--phone` | `-p` | Phone number (E.164 format) |\n| `--key` | `-k` | Loqate API key (overrides env) |\n| `--policy` | | Policy name: `strict`, `shipping`, `standard`, `permissive` |\n| `--policy-file` | | Path to custom policy JSON file |\n| `--batch` | `-b` | CSV/TSV/pipe-delimited file path (or `-` for stdin) |\n| `--delimiter` | `-d` | Batch delimiter: `comma`, `tab`, `pipe` (auto-detected if omitted) |\n| `--output` | `-o` | Output format: `json`, `jsonl`, `table` |\n| `--summary` | `-s` | Show batch summary statistics |\n| `--field` | | Extra Loqate input field `Key=Value` (repeatable) |\n| `--option` | | Loqate API option `Key=Value` (repeatable, dot notation for nesting) |\n| `--jsonl` | | JSON Lines output (one object per line) |\n| `--no-color` | | Disable color output |\n| `--verify-url` | | Custom address verification endpoint URL (overrides `LOQATE_VERIFY_URL` env var) |\n| `--verify-key` | | Custom address verification API key (overrides `LOQATE_VERIFY_KEY` env var). When set, `--key` is not required for address-only verification. |\n| `--verbose` | `-v` | Show reasoning log |\n\n**Examples:**\n\n```bash\n# Simple address verification\nlqt verify -a \"1600 Amphitheatre Parkway, Mountain View, CA 94043, US\"\n\n# Multi-field verification with strict policy\nlqt verify -a \"221B Baker St, London, GB\" \\\n -e \"sherlock@example.com\" \\\n -p \"+442071234567\" \\\n --policy strict\n\n# JSON output for piping to other tools\nlqt verify -a \"10 Downing St, London, GB\" -o json | jq '.address.confidence'\n\n# Extended input fields\nlqt verify -a \"125 Summer St\" --field Organization=\"Acme Corp\" --field Building=\"Suite 200\"\n\n# API options (dot notation for nesting)\nlqt verify -a \"125 Summer St, Boston, MA 02110, US\" --option GeoCode=true\n```\n\nFull list of input fields and API options: [Loqate International Batch Cleanse API](https://docs.loqate.com/api-reference/address-verify/international-batch-cleanse)\n\n### parse\n\nParse and standardize contact data using Claude (Haiku). Extracts address components, validates email syntax, and normalizes phone numbers with awareness of 250+ country-specific postal formats. No Loqate API calls — no credits spent.\n\n```bash\nlqt parse [flags]\n```\n\n**Flags:**\n\n| Flag | Short | Description |\n|------|-------|-------------|\n| `--address` | `-a` | Full address to parse |\n| `--email` | `-e` | Email address to validate |\n| `--phone` | `-p` | Phone number to normalize |\n| `--country` | `-c` | ISO 2-letter country code hint |\n| `--batch` | `-b` | CSV/TSV/pipe-delimited file path (or `-` for stdin) |\n| `--delimiter` | `-d` | Batch delimiter: `comma`, `tab`, `pipe` (auto-detected if omitted) |\n| `--output` | `-o` | Output format: `json`, `jsonl`, `table` |\n| `--jsonl` | | JSON Lines output |\n| `--no-color` | | Disable color output |\n| `--anthropic-key` | | Anthropic API key (overrides env) |\n\n**Examples:**\n\n```bash\n# Parse a messy address into structured components\nlqt parse -a \"125 summer street boston ma 02110 us\"\n\n# Parse address + validate email + normalize phone\nlqt parse -a \"10 downing st london\" -e \"test@mailinator.com\" -p \"02071234567\"\n\n# Batch parse from CSV\nlqt parse --batch messy-data.csv --output json\n```\n\n### policy\n\nList, inspect, and validate verification policies.\n\n```bash\nlqt policy list # List all built-in policies\nlqt policy show # Show full JSON for a policy\nlqt policy validate # Validate a custom policy JSON file\n```\n\n### mcp\n\nStart an MCP (Model Context Protocol) server. Exposes LQT as tools for AI agents.\n\n```bash\nlqt mcp # Stdio transport (launched by clients)\nlqt mcp --http :8080 # HTTP transport (deployed as a service)\nlqt mcp --smoke-test # Verify the server starts correctly and exit\n```\n\n**Flags:**\n\n| Flag | Default | Description |\n|------|---------|-------------|\n| `--http` | | Listen address (e.g. `:8080`, `127.0.0.1:8080`) |\n| `--rate-limit` | `10` | Max requests/sec per IP (`0` to disable) |\n| `--rate-burst` | `20` | Max burst size for rate limiter |\n| `--smoke-test` | | Self-test the MCP server (checks tools and prompts register) and exit |\n| `--disable-custom-endpoint` | | Block per-request custom verify endpoint fields |\n\n---\n\n## Policies\n\nPolicies control what gets accepted, reviewed, or rejected. Every verification runs through a policy — there are no hardcoded thresholds.\n\n| Policy | Addr Confidence | Match Level | Email Confidence | Phone Required | Use Case |\n|--------|:-:|:-:|:-:|:-:|------|\n| **strict** | 0.90 | premise | 0.85 | yes | KYC, fraud prevention, regulated |\n| **shipping** | 0.70 | street | 0.50 | no | Physical delivery, ecommerce |\n| **standard** | 0.55 | street | 0.45 | no | General verification (default) |\n| **permissive** | 0.30 | locality | 0.30 | no | Lead capture, early funnel |\n\n### Custom Policies\n\nCreate a JSON file:\n\n```json\n{\n \"name\": \"my-custom-policy\",\n \"description\": \"Tuned for my use case\",\n \"address\": {\n \"min_confidence\": 0.65,\n \"min_match_level\": \"street\",\n \"reject_verification_status\": [\"U\", \"R\"]\n },\n \"email\": {\n \"min_confidence\": 0.50,\n \"allow_catch_all\": true,\n \"reject_disposable\": true\n },\n \"phone\": {\n \"min_confidence\": 0.40,\n \"required\": false\n }\n}\n```\n\n```bash\nlqt policy validate my-policy.json # Validate first\nlqt verify -a \"...\" --policy-file my-policy.json\n```\n\n---\n\n## Batch Processing\n\nProcess files with address, email, and phone columns. Supports comma, tab, and pipe delimited input.\n\n```bash\n# CSV (auto-detected)\nlqt verify --batch addresses.csv --policy shipping -o json > results.json\n\n# Tab-delimited\nlqt verify --batch addresses.tsv -o json\n\n# Pipe-delimited\nlqt verify --batch addresses.txt --delimiter pipe -o json\n\n# From stdin\ncat addresses.csv | lqt verify --batch - --policy standard\n\n# With summary statistics\nlqt verify --batch addresses.csv --summary\n```\n\n**Windows (PowerShell):**\n```powershell\n.\\lqt.exe verify --batch addresses.csv --policy shipping -o json > results.json\nGet-Content addresses.csv | .\\lqt.exe verify --batch - --policy standard\n```\n\n### Delimiters\n\nAuto-detected from the first line. Override explicitly with `--delimiter`:\n\n| Value | Aliases | Description |\n|-------|---------|-------------|\n| `comma` | `csv` | Comma-separated (default) |\n| `tab` | `tsv` | Tab-separated |\n| `pipe` | | Pipe-separated |\n\n### Supported Columns\n\nUse a single `address` column or structured fields — or both. All column names are case-insensitive. Every field from the [Loqate International Batch Cleanse API](https://docs.loqate.com/api-reference/address-verify/international-batch-cleanse) is supported.\n\n**Address lines:**\n\n| Field | Accepted column names |\n|-------|----------------------|\n| Address (line 1) | `address`, `address1`, `street`, `address_line_1` |\n| Address lines 2-8 | `address2`-`address8`, `address_line_2`-`address_line_8` |\n| Delivery address | `deliveryaddress`, `delivery_address` |\n| Delivery lines 1-8 | `deliveryaddress1`-`deliveryaddress8`, `delivery_address_1`-`delivery_address_8` |\n\n**Geography:**\n\n| Field | Accepted column names |\n|-------|----------------------|\n| City | `city`, `locality`, `town` |\n| State/Province | `state`, `admin_area`, `province`, `region`, `administrative_area` |\n| County | `county`, `sub_admin_area`, `sub_administrative_area` |\n| Postal code | `postcode`, `postal_code`, `zip`, `zipcode` |\n| Country | `country`, `country_code` |\n\n**Street / building / premise:**\n\n| Field | Accepted column names |\n|-------|----------------------|\n| Street name | `thoroughfare`, `street_name` |\n| Building | `building`, `building_name` |\n| House number | `premise`, `house_number`, `building_number` |\n| Apartment/Suite | `sub_building`, `apartment`, `suite`, `unit`, `flat` |\n\n**Organization / postal:**\n\n| Field | Accepted column names |\n|-------|----------------------|\n| Organization | `organization`, `organisation`, `company`, `company_name` |\n| PO Box | `post_box`, `postbox`, `po_box`, `pobox` |\n\n**Contact / person:**\n\n| Field | Accepted column names |\n|-------|----------------------|\n| First name | `forename`, `first_name` |\n| Last name | `surname`, `last_name` |\n| Full name | `full_name`, `name` |\n\n**Non-address fields:**\n\n| Field | Accepted column names |\n|-------|----------------------|\n| Email | `email`, `email_address` |\n| Phone | `phone`, `telephone`, `phone_number`, `mobile` |\n\n### Example CSV\n\n```csv\naddress,email,phone,country\n\"125 Summer St, Boston, MA 02110\",user@example.com,+16175551234,US\n\"10 Downing St, London\",pm@gov.uk,+442071234567,GB\n```\n\n---\n\n## MCP Integration\n\nThe `lqt mcp` command exposes LQT as tools for AI agents via the [Model Context Protocol](https://modelcontextprotocol.io/). Connecting the MCP server also provides a built-in usage guide prompt that teaches the AI how to use the tools effectively.\n\n### Claude Code / Cursor\n\nAdd to your project's `.mcp.json`:\n\n```json\n{\n \"mcpServers\": {\n \"loqate\": {\n \"command\": \"lqt\",\n \"args\": [\"mcp\"],\n \"env\": {\n \"LOQATE_API_KEY\": \"your-key-here\",\n \"ANTHROPIC_API_KEY\": \"your-key-here\"\n }\n }\n }\n}\n```\n\n### Claude Desktop\n\nAdd to Claude Desktop's MCP settings:\n\n```json\n{\n \"mcpServers\": {\n \"lqt\": {\n \"command\": \"/usr/local/bin/lqt\",\n \"args\": [\"mcp\"],\n \"env\": {\n \"LOQATE_API_KEY\": \"your-key-here\",\n \"ANTHROPIC_API_KEY\": \"your-key-here\"\n }\n }\n }\n}\n```\n\n### GBG-hosted endpoint (recommended)\n\nThe fastest way to use Loqate over MCP is the GBG-hosted endpoint — no install, no infrastructure. Point any MCP client at:\n\n```\nhttps://reach.prod.fabric.gbgplatforms.com/mcp\n```\n\n**Claude Code / Cursor / any MCP client** — `.mcp.json`:\n\n```json\n{\n \"mcpServers\": {\n \"loqate\": {\n \"url\": \"https://reach.prod.fabric.gbgplatforms.com/mcp\"\n }\n }\n}\n```\n\nRestart your client, then ask it to \"verify 125 Summer St, Boston, MA 02110, US\". It will discover the tools, call them, and explain the result.\n\n**Authenticate with your Loqate API key — pick one:**\n\n1. **Per-call** — pass `key` in the tool arguments (`{\"key\": \"YOUR-KEY\", \"address\": \"...\"}`).\n2. **Connection-wide** — set `Authorization: Bearer ` on the HTTP connection. Applies to every tool call.\n3. **Out of band (Claude only)** — put `YOUR-KEY` in org / project / user instructions; the model injects it as `key` automatically.\n\nIf you supply none of the three, the server returns a `NO_API_KEY` error. The Bearer header only supplies the standard Loqate key; `verify_key` for a custom address-verify endpoint is separate.\n\n**Sanity check from your terminal** (no client needed):\n\n```bash\n# List tools (no auth required)\ncurl -s -X POST https://reach.prod.fabric.gbgplatforms.com/mcp \\\n -H 'Content-Type: application/json' \\\n -H 'Accept: application/json, text/event-stream' \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}'\n\n# Verify an address (Bearer auth)\ncurl -s -X POST https://reach.prod.fabric.gbgplatforms.com/mcp \\\n -H 'Authorization: Bearer YOUR-LOQATE-KEY' \\\n -H 'Content-Type: application/json' \\\n -H 'Accept: application/json, text/event-stream' \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/call\",\"params\":{\"name\":\"verify_address\",\"arguments\":{\"address\":\"125 Summer St, Boston, MA 02110, US\"}}}'\n```\n\nHosted deployments disable custom verify endpoints for security. If you receive a `CUSTOM_ENDPOINT_DISABLED` error, remove `verify_url` and `verify_key` from your tool arguments.\n\n### Remote HTTP (self-hosted)\n\nIf you'd rather run the server yourself, deploy `lqt mcp --http` as a service:\n\n```json\n{\n \"mcpServers\": {\n \"loqate\": {\n \"url\": \"https://lqt.your-company.com/mcp\"\n }\n }\n}\n```\n\nSame three-tier key resolution applies (body `key` → `Authorization: Bearer` → server env `LOQATE_API_KEY`).\n\n### Available Tools\n\n9 tools in stdio mode, 6 in HTTP mode (tools marked *stdio mode only* are not available over HTTP).\n\n| Tool | Description |\n|------|-------------|\n| `verify_address` | Verify an address with confidence score and recommendation |\n| `verify_email` | Verify an email with risk level and recommendation |\n| `verify_phone` | Verify a phone number with type/carrier and recommendation |\n| `verify_contact` | Verify all fields together with overall recommendation |\n| `parse_address` | Parse and standardize an address via Claude (stdio mode only) |\n| `list_policies` | List available decisioning policies |\n| `show_policy` | Show details for a specific policy |\n| `set_policy` | Register a custom policy (stdio mode only) |\n| `recommend_policy` | Get a recommended policy for your use case (stdio mode only) |\n\n---\n\n## Exit Codes\n\nDesigned for scripting and CI/CD:\n\n| Code | Meaning |\n|:---:|---------|\n| **0** | ACCEPT — all fields passed verification |\n| **1** | REVIEW — manual review recommended |\n| **2** | REJECT — verification failed |\n| **3** | ERROR — missing key, invalid input, API failure |\n\n**macOS / Linux:**\n```bash\nlqt verify -a \"125 Summer St, Boston, MA 02110, US\" --policy shipping -o json\ncase $? in\n 0) echo \"Ship it\" ;;\n 1) echo \"Queue for review\" ;;\n 2) echo \"Bad address\" ;;\n 3) echo \"Something broke\" ;;\nesac\n```\n\n**Windows (PowerShell):**\n```powershell\n.\\lqt.exe verify -a \"125 Summer St, Boston, MA 02110, US\" --policy shipping -o json\nswitch ($LASTEXITCODE) {\n 0 { Write-Host \"Ship it\" }\n 1 { Write-Host \"Queue for review\" }\n 2 { Write-Host \"Bad address\" }\n 3 { Write-Host \"Something broke\" }\n}\n```\n\n---\n\n## API Keys\n\n### Loqate API Key (for `verify`)\n\n**macOS / Linux:**\n```bash\n# Environment variable\nexport LOQATE_API_KEY=your-key-here\n\n# Key file (add to .gitignore)\necho \"your-key-here\" > .loqate-key\n\n# Per-command flag\nlqt verify -a \"...\" --key your-key-here\n```\n\n**Windows (PowerShell):**\n```powershell\n# Current session\n$env:LOQATE_API_KEY=\"your-key-here\"\n\n# Persistent (survives restarts)\n[System.Environment]::SetEnvironmentVariable(\"LOQATE_API_KEY\", \"your-key-here\", \"User\")\n\n# Per-command flag\n.\\lqt.exe verify -a \"...\" --key your-key-here\n```\n\n### Anthropic API Key (for `parse`)\n\n**macOS / Linux:**\n```bash\nexport ANTHROPIC_API_KEY=your-key-here\n```\n\n**Windows (PowerShell):**\n```powershell\n$env:ANTHROPIC_API_KEY=\"your-key-here\"\n```\n\n**Resolution order:** flag > environment variable > key file\n\n### Custom Verify Endpoint (optional)\n\nIf you need to route address verification through a different endpoint (e.g., an on-premises or partner-hosted Loqate instance):\n\n**macOS / Linux:**\n```bash\n# Environment variables\nexport LOQATE_VERIFY_URL=https://custom-verify.example.com/v1/batch\nexport LOQATE_VERIFY_KEY=your-custom-key\n\n# Or use flags (override env vars)\nlqt verify -a \"...\" --verify-url https://custom-verify.example.com/v1/batch --verify-key your-custom-key\n```\n\n**Windows (PowerShell):**\n```powershell\n$env:LOQATE_VERIFY_URL=\"https://custom-verify.example.com/v1/batch\"\n$env:LOQATE_VERIFY_KEY=\"your-custom-key\"\n```\n\n**Resolution order:** flag > environment variable > default Loqate endpoint\n\nWhen `--verify-key` is set, the standard `--key` / `LOQATE_API_KEY` is not required for address-only verification. If you also verify email (`-e`) or phone (`-p`), the standard key is still needed for those.\n\nThese flags only affect address verification. Email and phone always use the standard Loqate endpoints.\n\nIn MCP mode, clients can pass `verify_url` and `verify_key` per-request in `verify_address` and `verify_contact` tool inputs.\n\n---\n\n## Support\n\n- **Bug reports & feature requests** — [open an issue](https://github.com/gbgplc/lqt/issues/new/choose)\n- **Security vulnerabilities** — please email [labs@gbg.com](mailto:labs@gbg.com) instead of opening a public issue\n- **General questions** — [start a discussion](https://github.com/gbgplc/lqt/discussions) or open an issue\n\nWhen reporting a bug, please include:\n- `lqt` version (`lqt --version`)\n- OS and architecture (e.g., macOS ARM64, Linux x86_64)\n- The command you ran (redact any API keys)\n- Expected vs actual behavior\n\n---\n\n## License\n\nProprietary — see [LICENSE](https://github.com/gbgplc/lqt/blob/main/LICENSE). Use requires an active Loqate subscription.\n\n---\n\n

\n Built by GBG.\n

\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"categoryDisplayName","Communication","upstream",{"_95":96,"_97":98,"_99":-5,"_100":101,"_102":-5},"requiredSecrets",[],"tags",[],"assets",[],"stats",{"_93":80,"_94":80},"ratingAvg","reviewCount","topics",[],"license","NOASSERTION","language","registryName","io.github.gbgplc/lqt","homepage","ENV",{"_105":106,"_107":108,"_109":110},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]