Every address, placed and zoned.

One API validates, geocodes and zones every address in your business systems, and shows its working on a map.

  • Autocomplete
  • Standardise
  • Geocode
  • Enrich
  • Zone

A live call to the AddressIQ demo API on a small synthetic Australian dataset. Not live provider data. Click the map to zone any point.

Demo zones, synthetic data

Loading the demo…

    Plugs into the systems you already run

    SalesforceServiceNowSAPDynamics 365IBM MaximoOracleNetSuiteExcel

    Routes across the geocoders you choose

    Authoritative national sourcesCommercial global geocodersOpen dataSelf-hosted routing

    Names show compatibility, not endorsement or partnership. Provider marks belong to their owners.

    1 API
    in place of every system times every provider integration
    5 stages
    autocomplete, standardise, geocode, enrich, zone
    9
    geocoding providers in the roster, authoritative to open-source
    $0
    SAP subscription needed: the same product runs as Docker or Kubernetes

    Five stages, one call.

    You send402 collins st melbYou get backOne record, with reasons1Autocomplete402 Collins St,Melbourne VIC 30002Standardisesuburb: Melbournepostcode: 30003Geocode-37.817, 144.960+ precision, confidence4EnrichLGA: Melbourne+ flood risk, zoning5Zonezone: Inner Metro+ the rule that wonprovider callprovider callRouting layerpicks the provider, checks its licence, meters the call
    One call carries the address through all five stages. Example values; zone names in the demo are synthetic.

    Autocomplete

    Suggestions from the first provider that answers.

    Standardise

    One canonical address object, whichever provider replied.

    Geocode

    Coordinates with stated precision and confidence.

    Enrich

    LGA, flood risk, zoning and electorate in one governed pipeline.

    Zone

    The zone each point falls in, weighted and explainable.

    Provider licences are enforced at the routing layer: caching and storage rights per provider, every call metered for audit.

    From a typed address to a decision you can defend.

    Each address passes through the same five stages. Every result says which provider answered, how precise it is, and which zone rule won.

    Autocomplete and validate

    Suggestions as the user types, from the first provider that answers. The result is one canonical address with a verified, partial or unverifiable status.

    18 beach
    18 Beach Rd, Bondi NSW 2026
    18 Beach St, Coogee NSW 2034
    StatusVerified

    Example values come from the synthetic demo dataset. SA1 is not built yet. Live road routing needs a routing engine connected; the demo returns estimates. Bulk jobs and the console are alpha: built and tested on a test database with mocked sign-in. The console has no self-serve sign-up, no real identity-provider login and has not been timed with a new user. Bulk jobs are tested at 1,000 rows; 10,000 is not yet run.

    See every zone on one map.

    Switch layers on and off, then click anywhere to see which zones contain that point and which one wins.

    Zones drawn here are the demo set. In the product you create them from an admin boundary or draw them by hand, in the Zone Manager.

    Install it where your teams work.

    One plugin per platform: autocomplete and validation on the form, enrichment and zone written back to the record.

    Salesforce

    Lightning component for Flow and record pages.

    Wrapper · alpha

    ServiceNow

    UI Builder component for asset and CMDB forms.

    Wrapper · alpha

    SAP

    Fiori and UI5 control, on BTP or standalone.

    Wrapper · alpha

    Dynamics 365

    Power Apps field control, plus an Excel Power Query connector.

    Wrapper · alpha

    Maximo

    Work-order and asset location.

    Planned

    Oracle and NetSuite

    Customer, vendor and site addresses.

    Planned

    Any web app

    One web component: a tag, a key, an event.

    Beta

    Marketplace listings (AppExchange, ServiceNow Store, SAP Store) are on the roadmap, not live yet.

    One call. The whole answer.

    Type an address and watch the real response from the demo API.

    
      
    Waiting for the first call…
    
    
    
    
    The OpenAPI spec, Postman collection, bulk jobs, webhook verification and MCP set-up are in the developer docs.
    
  
    

    


    
  
    
    
    One geocoder, or one address layer?
    
    
    A geocoder answers where an address is. Your business also needs to know what it belongs to, and to trust the answer.
    
    
    Wired system by systemOne address layerCRMCRMService deskService deskERPERPAsset managementAsset managementProvider AProvider AProvider BProvider BProvider CProvider CAddressIQroutesfalls backlicence ruleszones7 connections, each with its own code, licence terms and outages4 plugins in, one routing layer out
    The same four systems and three providers, wired two ways.
    
    
    
      
    A single geocoder API
      
        
    • One provider's data, one provider's licence and outages
      • 
        
    • Each system integrated and maintained on its own
      • 
        
    • A point on a map; zones and business rules are yours to build
      • 
        
    • A result without the reason behind it
      • 
        
    • No help turning words, files or agents into valid addresses
    
      
    AddressIQ
      
        
    • Routes across providers and falls back, with licence rules enforced per provider
      • 
        
    • One plugin pattern for Salesforce, ServiceNow, SAP, Dynamics, Maximo and Oracle
      • 
        
    • Zones and enrichment on every address, ranked and deterministic
      • 
        
    • Every result names the provider that answered and the rule that won
      • 
        
    • AI that proposes and a person that confirms, plus MCP tools for your own agents
    
    
    
  
    

    


    
  
    
    
    What duplication costs.
    
    
    Move the sliders to your estate. Figures use assumptions (not measured customer results) for integration build and maintenance effort and published provider pricing; the briefing replaces them with your real numbers.
    
    
    
      
    
        
        
        
        
        
        
        
        
        
        
        
        
    Benefit is shown net of what you would pay us. An ROI model that hides its own cost line does not survive CFO diligence.
    
      
    
      
    
        
    Estimated 3-year net benefit
    
        
    $—
    
        
    Integration build avoided (N−1 systems × ~25 days)$—
    
        
    Annual maintenance avoided (~20% of build, 3 yrs)$—
    
        
    Provider cost optimisation (authoritative or cheap-first routing)$—
    
        
    Forced provider migration, done once, not per system$—
    
        
    Match-rate uplift (~9pp fewer failed lookups needing manual fix @ $4.20 ea)$—
    
        
    Less: AddressIQ cost over 3 years−$—
    
        
    Model: build 25 engineer-days per additional system integration; maintenance 20% of build per year; provider saving = volume × (current blend − optimised $0.0009/call authoritative-first blend), floor 0; provider migration 30 days once vs per affected system; failed-lookup remediation $4.20/record on 15% of the 9pp of volume improved; minus 3 × your AddressIQ annual cost estimate. Conservative by design; the briefing replaces every input with your real numbers.
    
      
    
    
    
  
    

    


    
  
    
    
    See your addresses resolved.
    
    
    A 45-minute briefing: we run a sample of your own addresses through the aggregator and show the match rate and provider-cost difference against your current setup.
    
    addressiq@vrdigital.solutions