AI in AddressIQ.

AI proposes, a person confirms and the engine decides. Your own agents get read-only tools through MCP.

AI that proposes. The engine decides.

AI drafts, a person or a rule confirms, and the geocoder and zone engine stay deterministic. That keeps every answer repeatable and every change reviewable.

  • Never writes by itself. Every proposal needs a confirmation before it is saved. Off by default for each tenant until a platform administrator switches it on.
  • Answers only from your own zones, usage and mappings, and ignores instructions hidden inside address text.
  • Works with no AI key: you get the grounded data instead of a narrative.
  • The geocoding path never calls a language model. AI spend is metered in the same ledger as provider spend.

  • In the product now (alpha)

  • Draw a zone in words

    Alpha

    Saves the hour spent in the zone editor. Describe a postcode range, a suburb or a state and get a draft zone with its boundary previewed. Longer rules such as drive-time or exclusions are planned.

    Postcodes 2020 to 2035, ranked firstDraft zone and map preview. Nothing is saved until you confirm.

  • Map your fields

    Alpha

    Turns a connector project from days into minutes. Paste one record from a SAP, Salesforce or Maximo table and get the suggested field mapping, including traps such as latitude held in a Y coordinate field.

  • Ask the geo-assistant

    Alpha

    Answers in plain language, from your data. Ask which zones exist, how many calls ran and what was spent. It is read-only, and tells you which admin action to run if you ask for a change.

  • Cut provider cost

    Alpha

    Spots money and delay in your own traffic. Reads your usage ledger and tells you when requests cascade past the first provider or one provider drives most of the spend.

  • Give your own AI agents a map

    Alpha

    Stops agents guessing addresses. Eight read-only tools (validate, autocomplete, reverse geocode, zone by point or address, enrich, bulk, drive distance) for any MCP-capable assistant, with the same key, scopes and limits as the API. Runs over stdio from your machine; no hosted transport. Tested against a mock API; not yet run against the live service.

  • Next

  • Fix messy addresses

    Planned

    Rescues call-centre notes, scanned forms and free text. AI proposes the structure, then a real provider must confirm the address exists. It is never allowed to invent one.

  • Triage a bulk file

    Planned

    Turns 2,000 exceptions into a handful of causes. Groups unmatched rows by reason and offers one-click fixes you accept or reject.

  • Merge duplicates across systems

    Planned

    One place, one identity. Borderline matches between SAP, Salesforce and ServiceNow records are judged with the reason shown, then a person confirms. Needs the Address Hub.

  • Tell me what moved

    Planned

    Boundary changes without the surprise. When a ward, postcode or your own zone changes, get a summary of how many customers changed zone before you publish.

Give your AI agents a map.

Language models guess addresses. Connect the AddressIQ MCP server and your assistant checks them against real providers instead, and says so when it cannot.

validate_addressautocomplete_addressreverse_geocodezone_for_pointzone_for_addressenrich_addressbulk_validatedrive_distance

Read-only by design: no tool can create, change or delete anything. The key stays in your environment and is never sent to the model.

{
  "mcpServers": {
    "addressiq": {
      "command": "node",
      "args": ["/path/to/addressiq/mcp/server.js"],
      "env": {
        "ADDRESSIQ_URL": "https://your-addressiq-host",
        "ADDRESSIQ_KEY": "your-api-key"
      }
    }
  }
}
Your environmentYour assistantthe language modelMCP serverholds the API keyAddressIQ APIchecks and zonesProvidersaddress datatool callchecked resultHTTPS + keyNo key reaches the model.8 tools, all read-only: none can create, change or delete.
The API key travels on one hop only, from your MCP server to AddressIQ.