AddressFinder API

Name: AddressFinder API
Brand: AddressFinder API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentAddress ValidationapiKey10 EndpointsREST

For Agents

Search and verify Australian and New Zealand addresses, look up suburbs and postcodes, and verify email addresses. Used by AU/NZ-focused checkout, signup, and CRM hygiene agents.

Install Jentic One Beta

Connect the AddressFinder API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AddressFinder API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AddressFinder API.

Search Australian addresses with type-ahead matching to power autocomplete fields

Retrieve full metadata for a specific Australian address including DPID and geocode

Search New Zealand addresses with the same autocomplete pattern

GET STARTED

Start building with AddressFinder API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AddressFinder API for, with concrete tasks.

★ Address autocomplete on AU/NZ checkout

E-commerce stores shipping to Australia or New Zealand integrate AddressFinder's /au/address and /nz/address endpoints to power type-ahead address fields. As the shopper types, the API returns ranked candidates so the user picks a verified address in two or three keystrokes. This reduces invalid-address shipping errors and shortens checkout time noticeably.

On each keystroke after three characters, GET /au/address with q set to the partial input and return the top five candidates as suggestions.

CRM address hygiene

Sales operations periodically clean their CRM by re-validating customer addresses. For each AU or NZ record, the agent calls /au/address/info or /nz/address/info to confirm the address still maps to a known DPID and to standardise formatting. Records that fail validation are flagged for manual review, while passes are upgraded with the canonical address string and geocode.

For each customer with country AU, GET /au/address/info with the existing address; if it returns a valid DPID, write the canonical formatted_address back to the CRM.

Email verification on signup

Marketing teams want to suppress disposable, mistyped, or undeliverable emails before they reach the email service provider. The /email/v1/verification endpoint returns a deliverability verdict and metadata so signup forms can reject obvious bad inputs and the back-end can defer marketing sends for risky ones. This keeps sender reputation higher and reduces wasted credits.

On signup form submit, GET /email/v1/verification with the entered email and reject the form if the response status is 'undeliverable' or 'invalid'.

AI agent address validation via Jentic

An AI agent in a contact-centre app uses Jentic to validate an Australian address dictated over the phone. The agent searches 'verify australian address', loads the GET /au/address/info schema, fills the address string from the transcript, and confirms the DPID match back to the operator. The AddressFinder API key never enters the agent's context - Jentic adds it from your Jentic One instance.

Use Jentic to search 'verify an australian address', load the GET /au/address/info schema, and execute with q set to the dictated address.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for addressfinder api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/au/address

Search Australian addresses

GET

/au/address/info

Get detailed Australian address information

GET

/nz/address

Search New Zealand addresses

GET

/nz/address/info

Get detailed New Zealand address information

GET

/au/location

Search Australian locations

GET

/nz/location

Search New Zealand locations

GET

/email/v1/verification

Verify an email address

GET

/au/address

Search Australian addresses

GET

/au/address/info

Get detailed Australian address information

GET

/nz/address

Search New Zealand addresses

GET

/nz/address/info

Get detailed New Zealand address information

GET

/au/location

Search Australian locations

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AddressFinder API key is stored once, encrypted, by your own Jentic One instance and appended to the key parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'autocomplete an australian address', and Jentic returns the matching AddressFinder operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because AddressFinder does not publish a public OpenAPI spec.

Time to first call

FAQs

Specific to using AddressFinder API through Jentic.

Why is there no official OpenAPI spec for AddressFinder API?

AddressFinder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AddressFinder API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the AddressFinder API use?

AddressFinder uses an API-key scheme: a key issued in the AddressFinder dashboard is sent as the key query parameter. Jentic keeps the key in your Jentic One instance and appends it at execute time so it never appears in agent context, even though it travels on the URL.

Can I look up Australian and New Zealand addresses with the same API key?

Yes. The /au/address and /nz/address endpoints share authentication - one key works for both countries. Use /au/address/v2 when v1 returns ambiguous matches and you want the refined ranking.

How do I validate an address through Jentic?

Search Jentic for 'verify australian address' or 'verify new zealand address', load the GET /au/address/info or /nz/address/info schema, and execute with q set to the address string. The response includes the DPID, formatted address, and geocode.

Are there rate limits on the AddressFinder API?

AddressFinder applies per-account credit and rate limits scaled to plan; the spec does not declare a fixed RPS value. When 429 responses occur Jentic surfaces them so retry logic can read the Retry-After header.

Does this API support countries other than Australia and New Zealand?

No. The address-related endpoints are scoped to AU and NZ datasets only. For US, UK, or global address validation, use a competing provider such as Smarty, Loqate, or HERE.

Can I limit what my agent is allowed to do with the AddressFinder API?

Yes. Because you run Jentic One self-hosted, your own rules decide which AddressFinder operations and credentials the agent may use. These endpoints are read-only lookups that pass the key and query in the URL, so you can allow just the ones the agent needs, such as autocompleting an Australian address through /au/address, while withholding New Zealand lookups or the /email/v1/verification endpoint. The API key is held by your Jentic One instance and appended only for the operations you have permitted.