Reference & Lookup Data · Integration
Addressfinder
Add Addressfinder to your product for your customers, and give your AI agents governed access to it.
Addressfinder's API is at api.addressfinder.io with country specific paths, for example /api/nz/address/autocomplete and the matching Australian routes, authenticated with a licence key plus a secret for server to server calls. Address lookup is deliberately two steps: autocomplete returns candidate addresses with an id, then the metadata endpoint returns the full structured record for the chosen id including postcode, region and geocode, so storing only the autocomplete label loses the data you actually wanted. Browser side calls do not send the secret and instead rely on domains registered in the portal, which means a customer's new domain will fail until someone adds it. Coverage is deepest for New Zealand and Australia against official address datasets, with other countries served by separate international endpoints of differing depth. Requests are metered per lookup against the plan, so a typeahead field needs debouncing or it burns quota on every keystroke. fastn holds each customer's key and secret, keeps the two step flow together and handles upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Addressfinder licence so lookups run on their plan and their registered domains
Add address autocomplete to a signup or checkout form and store the structured metadata rather than a single text line
Verify addresses already in a customer's database and flag the ones that no longer match an official record
Capture geocodes at entry so downstream routing and territory logic have coordinates without a second provider
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to verify an address on a record and report which components were corrected
Have an agent standardise a batch of addresses, with lookups audited per tenant against that customer's quota
Let an agent check whether a delivery address is deliverable before an order is confirmed
Example prompt
Can you verify this delivery address in Wellington and give me the postcode and coordinates?
Set up Addressfinder in 4 steps
- 01Enable the Addressfinder connector from your fastn dashboard.
- 02Have each customer authorise their own Addressfinder account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Addressfinder integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Addressfinder integration without building it. Your customers connect their own Addressfinder account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Addressfinder update is not your on-call problem.
- One integration serves your product and your agents. The same governed Addressfinder connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Addressfinder, across other categories.
Salesforce
HubSpot
Notion
SnowflakeAddressfinder integration FAQ
How do I add an Addressfinder integration to my product?
Enable the Addressfinder connector in your fastn dashboard, then let each customer authenticate their own Addressfinder account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Addressfinder client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Addressfinder account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Addressfinder account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Addressfinder integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to verify an address on a record and report which components were corrected
Who maintains the Addressfinder integration?
fastn does. When Addressfinder changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does an Addressfinder lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Addressfinder results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Addressfinder is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Addressfinder integration?
A common starting point: let a customer connect their own Addressfinder licence so lookups run on their plan and their registered domains. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Addressfinder integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Addressfinder does not change your per-connector cost. You can start free with 3 connected accounts.
Add Addressfinder to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.