Reference & Lookup Data · Integration
Address Validator
Add Address Validator to your product for your customers, and give your AI agents governed access to it.
Embed address validation so your customers can verify and normalise postal addresses inside your product, and so your agents can check an address before acting on it. fastn handles each customer's credentials and API upkeep, so validation is a configuration step rather than a service you operate.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Validate an address at the point of entry so bad data never lands in your product.
Normalise addresses to a consistent format before storing or shipping.
Flag undeliverable or incomplete addresses for review.
Bulk-check existing records to find addresses that need correcting.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent verifies an address before creating a shipment or invoice.
An agent normalises an address it was given in free text.
An agent flags a record whose address cannot be validated.
Example prompt
Validate the shipping addresses on today's orders and list any that came back undeliverable.
Set up Address Validator in 4 steps
- 01Open the address validation connector from your fastn dashboard.
- 02Have each customer supply their provider credentials.
- 03Enable the validation and normalisation actions your product uses.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Address Validator integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Address Validator integration without building it. Your customers connect their own Address Validator 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 Address Validator update is not your on-call problem.
- One integration serves your product and your agents. The same governed Address Validator 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
Works well with
AfterShip
Shopify
NetSuiteOften used alongside
Tools the same teams tend to run next to Address Validator, across other categories.
Salesforce
HubSpot
Notion
SnowflakeAddress Validator integration FAQ
How do I add an Address Validator integration to my product?
Enable the Address Validator connector in your fastn dashboard, then let each customer authenticate their own Address Validator account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Address Validator client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Address Validator account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Address Validator 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 Address Validator integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent verifies an address before creating a shipment or invoice.
Who maintains the Address Validator integration?
fastn does. When Address Validator 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 Address Validator 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 Address Validator results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Address Validator 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 Address Validator integration?
A common starting point: validate an address at the point of entry so bad data never lands in your product. 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 Address Validator integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Address Validator does not change your per-connector cost. You can start free with 3 connected accounts.
Add Address Validator to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.