A reliably smart, reliably accurate data quality platform for address, email, and phone verification
A reliably smart, reliably accurate data quality platform for address, email, and phone verification On Nagent, Addressfinder is exposed as a fully-configurable developer tools integration that any agent can call — 17 actions, and API key authentication. No code is required to wire Addressfinder into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Addressfinder to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Addressfinder into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Addressfinder, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ADDRESSFINDER_AU_ADDRESS_AUTOCOMPLETE_APITool to perform interactive search of Australian addresses from the AddressFinder database. Use when you need to search for and autocomplete Australian addresses based on partial input.
Input parameters
The partial address being searched
Maximum results to return (1-100, default: 10)
Convert special characters: 1 for ASCII equivalents
Service identifier for activity monitoring
Response format: json or xml (default: json)
Address dataset source: GNAF, PAF, or GNAF,PAF (default)
Filter PO Box addresses: 0 (exclude), 1 (only), or omit (include all)
Return canonical/alias addresses: 1 (canonical only) or omit
Enable highlighting: 1 to wrap matches with <span class='af_hl'></span>
Comma-separated state filters (ACT, NSW, NT, QLD, SA, TAS, VIC, WA, OT)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_AU_ADDRESS_METADATATool to retrieve full metadata for an Australian address selected from the Address Autocomplete API. Use when you need complete address details including GPS coordinates and census data.
Input parameters
Unique address identifier from Address Autocomplete API. Must supply either id, gnaf_id, or dpid.
Set to '1' to include GPS coordinates in the response.
Australia Post delivery point identifier. Must supply either id, gnaf_id, or dpid.
Set to '1' to convert special characters to ASCII.
Census year - 2016 or 2021. Defaults to 2016.
Service identifier for activity monitoring.
Response format - 'json' or 'xml'. Defaults to json.
Address source - 'GNAF', 'PAF', or 'GNAF,PAF'. Defaults to GNAF,PAF.
Unique id from the G-NAF dataset. Must supply either id, gnaf_id, or dpid.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_AU_ADDRESS_VERIFICATIONTool to verify Australian addresses against PAF/GNAF databases. Use when you need to validate or standardize an Australian address and retrieve associated metadata like coordinates, statistical identifiers, and GNAF data.
Input parameters
Full address to be verified (e.g., '274 Harbour Drive, COFFS HARBOUR NSW 2450')
Include latitude/longitude coordinates when available. Set to '1' to enable.
Query PAF database for postal addresses. Set to '1' to enable (default).
Query GNAF database for physical addresses. Set to '1' to enable (default).
Convert special characters to ASCII equivalents. Set to '1' to enable.
Census year for statistical area identifiers (2016 or 2021).
Service identifier for activity monitoring.
Response format: 'json' or 'xml'. Defaults to 'json'.
Return additional GNAF data (lga_name, lga_type_code, gnaf_id, legal_parcel_id). Set to '1' to enable.
Set to '0' to exclude PO Box-type addresses from results.
Filter by state(s): ACT, NSW, NT, QLD, SA, TAS, VIC, WA, OT. Comma-separated for multiple states.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_AU_LOCATION_AUTOCOMPLETE_APITool to perform interactive autocomplete search for Australian streets, suburbs, and states. Use when you need to find or suggest Australian locations based on partial input.
Input parameters
Query string to match against Australian locations (streets, suburbs, states).
Maximum number of results to return, range 1-100. Defaults to 10.
Service identifier for Portal activity monitoring; must be registered in your account.
Response format - 'json' or 'xml'. Defaults to 'json'.
Secret key from Portal Credentials; required only for server-to-server calls.
Set to 1 to include highlighted matching terms wrapped in <span class='af_hl'></span>.
Comma-separated state/territory codes to filter by: ACT, NSW, NT, QLD, SA, TAS, VIC, WA, OT.
Comma-separated filter for location types: 'street', 'locality' (suburb), 'state'. Example: 'street,locality'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_AU_LOCATION_METADATA_APITool to retrieve comprehensive metadata for an Australian location (street, suburb, or state) selected from the Location Autocomplete API. Use when you need detailed information about a specific Australian location including coordinates, street details, suburb, state, and postcode.
Input parameters
Unique location identifier from the Location Autocomplete API. This identifies the specific street, suburb, or state to retrieve metadata for.
Optional service identifier for tracking activity in the Portal. Must be a registered domain.
Response format. Either 'json' or 'xml'. Defaults to 'json'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_EMAIL_VERIFICATION_APITool to verify email addresses including syntax validation, domain existence, and email account verification. Use when you need to validate an email address before sending messages or storing contact information.
Input parameters
The email address to be verified. Can contain spelling mistakes or errors that will be validated.
Used to identify which of your services is calling the API for activity monitoring purposes.
Response format - json or xml. Default is json.
Comma-separated list controlling verification methods: domain, connection, provider. Default: domain,connection
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_INT_ADDRESS_AUTOCOMPLETE_APITool to search for international addresses using autocomplete functionality. Use when users need to find and select addresses in supported countries (AU, BE, CA, CZ, DK, FR, DE, IE, NZ, NL, PT, SG, ES, SE, GB, US). Returns address IDs that can be used with the Address Metadata API to retrieve full address details.
Input parameters
Partial address search query. Maximum 200 characters. This is the text that users type to search for addresses.
Maximum number of results to return. Must be between 1 and 15 inclusive. Defaults to 10.
Service identifier for Portal activity monitoring. Must be registered in your account.
Response format - either 'json' or 'xml'. Defaults to 'json'.
Secret key from Portal Credentials. Required for server-to-server API calls.
ISO 3166 alpha-2 country code for the address search. Supported countries: au (Australia), be (Belgium), ca (Canada), cz (Czech Republic), dk (Denmark), fr (France), de (Germany), ie (Ireland), nz (New Zealand), nl (Netherlands), pt (Portugal), sg (Singapore), es (Spain), se (Sweden), gb (United Kingdom), us (United States).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_INT_ADDRESS_METADATA_APITool to retrieve full metadata for an international address selected from the Address Autocomplete API. Use when you need complete address details including street metadata and optional GPS coordinates for addresses outside your primary region.
Input parameters
Unique address identifier obtained from the Address Autocomplete API.
Include GPS coordinates in the response. Set to 1 to include, 0 to exclude. Default is 0.
Used to identify in the Addressfinder Portal which of your services is calling the API.
Response format: json or xml. Default is json.
ISO 3166 alpha-2 country code (e.g., fr, us, ca, gb, au, nz, be, cz, dk, de, ie, nl, pt, sg, es, se).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_ADDRESS_AUTOCOMPLETETool to perform interactive search for New Zealand addresses. Use when you need to find closely matching NZ addresses based on partial address input. The tool searches the Addressfinder database and returns matching addresses which can then be selected by the user. Works with the Address Metadata API to retrieve associated address data using the pxid identifier.
Input parameters
The partial address being searched. Provide the address query string to search for matching New Zealand addresses.
Maximum number of results to return. Defaults to 10. Valid range is 1-100.
Set to '1' to convert special characters to ASCII equivalents in the response.
Filter rural vs. urban addresses. Set to '0' for urban addresses only, '1' for rural addresses only.
Service identifier for activity monitoring. Used to track and monitor API usage by domain.
Response format - 'json' or 'xml'. Defaults to json.
Match strictness level. '0' for normal matching, '1' for strict matching, '2' for fuzzy matching.
Include or exclude PO Box style addresses. Set to '0' to exclude PO Boxes, '1' to include only PO Boxes.
Filter by NZ Post delivery status. Set to '0' to exclude delivered addresses, '1' to include only delivered addresses.
Set to '1' to wrap matching terms in highlighting span tags in the response.
Filter by NZ region code. Valid codes are 1-9 and A-H representing different New Zealand regions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_ADDRESS_METADATATool to retrieve full metadata for a NZ address including coordinates, census data, and postal details. Use after selecting an address from the Address Autocomplete API to get complete address information.
Input parameters
Unique reference number assigned to a delivery address by NZ Post
Unique address identifier obtained from the Address Autocomplete API
Set to 1 to convert special characters to ASCII equivalents
Data source year - 2018 or 2023. Default is 2023
Used to identify which service is calling the API for activity monitoring
Response format - json or xml
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_ADDRESS_REVERSE_GEOCODETool to reverse geocode NZ addresses from GPS coordinates. Use when you need to find the nearest addresses to a given longitude and latitude. Returns addresses ordered by distance.
Input parameters
Longitude in WGS84 format (example: 174.773068233188)
Latitude in WGS84 format (example: -41.2917018846201)
Maximum results to return (1-100, default: 10)
Service identifier for portal usage tracking; must be registered
Response format; accepts 'json' or 'xml'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_ADDRESS_VERIFICATION_APITool to verify New Zealand addresses against the Addressfinder database. Use when you need to validate and enrich NZ addresses, correct spelling mistakes, or retrieve detailed address metadata including coordinates and postal information.
Input parameters
The address to be verified. Can contain spelling mistakes.
ASCII conversion: '1' reformats special characters to ASCII equivalents.
Census year for statistics: 2018 or 2023. Default is 2023.
Service identifier for portal tracking purposes.
Response format: 'json' or 'xml'. Default is 'json'.
Secret key from Portal Credentials for server-to-server authentication.
Filter PO Box addresses: '0' excludes PO Boxes, '1' includes only PO Boxes.
Restrict search to specific NZ region. Valid codes are 1-H.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_LOCATION_AUTOCOMPLETETool to perform interactive search for New Zealand streets, suburbs, cities, and regions. Use when you need to find or autocomplete location names in New Zealand. Returns closely matching locations with unique identifiers for further metadata lookups.
Input parameters
Query string to match against locations (streets, suburbs, cities, regions). Maximum 200 characters.
Maximum number of results to return. Must be between 1 and 100. Default: 10
Set to '0' to exclude cities, '1' for cities only. Omit for all types.
Identifies calling service in Addressfinder Portal for analytics.
Response format - 'json' or 'xml'. Default: json
Set to '0' to exclude regions, '1' for regions only. Omit for all types.
Secret key from Portal Credentials; required for server-to-server calls.
Set to '0' to exclude streets, '1' for streets only. Omit for all types.
Match strictness - '0' (normal), '1' (strict), '2' (fuzzy). Default: '0'
Set to '0' to exclude suburbs, '1' for suburbs only. Omit for all types.
Set to 1 to highlight matched terms with '<span class="af_hl"></span>' tags.
Restrict results to specific region. Codes: 1-9, A-H (e.g., '1' for Northland, 'A' for Canterbury).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_LOCATION_METADATATool to retrieve full metadata for a New Zealand location selected from the Location Autocomplete API. Use when you need detailed information including coordinates and LINZ address data for a specific location.
Input parameters
Unique location identifier from the Location Autocomplete API.
Used to identify your calling service for usage tracking in the AddressFinder Portal. Must be registered in the Portal.
Response format - 'json' or 'xml'.
Secret key from Portal Credentials; only needed for server-to-server calls. Can also be passed via Authorization header.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZ_POI_AUTOCOMPLETE_APITool to perform interactive search for points of interest in New Zealand. Use when you need to find POIs like hospitals, cafes, or schools based on partial name matching.
Input parameters
The query string to match against POI names and addresses
Maximum results to return (1-100, default: 10)
Used to identify your service in the AddressFinder Portal
Response format; accepts 'json' or 'xml'
Set to 1 to include highlighted matching text with <span class='af_hl'></span>
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_NZPOI_METADATA_APITool to retrieve comprehensive metadata for New Zealand points of interest including coordinates and address details. Use when you need full POI information after selecting from autocomplete API.
Input parameters
Unique POI identifier from the autocomplete API
Service identifier in Addressfinder Portal (must be registered)
Response format - 'json' or 'xml'
Secret key from Portal Credentials (required for server-to-server calls)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ADDRESSFINDER_PHONE_VERIFICATION_APITool to verify phone numbers through syntax, range checks, and network verification. Use when you need to validate a phone number's format, line type, and connection status. Returns verified number details including line type, connection status, and formatted representations.
Input parameters
Service identifier for Portal activity monitoring.
Response format: 'json' or 'xml'. Defaults to 'json'.
Maximum wait time for verification in seconds.
Require the number to be a mobile phone. Set to True to restrict to mobile numbers only.
The phone number to be verified.
ISO2 country code used when phone lacks country calling code (e.g., 'AU', 'US', 'GB').
Comma-separated ISO2 country codes restricting valid countries (e.g., 'AU,NZ,US').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 48 agents privately built on Nagent that already use Addressfinder.
Build on Nagent
Connect Addressfinder to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Addressfinder, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Addressfinder is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Addressfinder is connected, you configure its 17 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Addressfinder steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Addressfinder event fires, the agent kicks off automatically.
Every Addressfinder action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Addressfinder ships with 17 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Addressfinder together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Addressfinder-based workflows tailored to your business.