Addressfinder for AI agents
Addressfinder verifies and autocompletes addresses, emails and phone numbers for Australia, New Zealand and beyond. Developers use it to keep checkout and signup forms accurate. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Addressfinder.
Autocomplete an Australian address
Suggest matching Australian addresses as a user types, to speed up a checkout or signup form.
Verify an address
Confirm a submitted address is real and deliverable before it is saved to a shipping record.
Verify a phone number
Check that a phone number is valid and correctly formatted before storing it against a customer record.
17 Addressfinder actions, graded by risk.
Every Addressfinder action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
17Create and change things. Allow, or ask the user first.
- addressfinder.nzpoi_metadata_apiGet NZ POI Metadata
- addressfinder.au_address_metadataGet AU Address Metadata
- addressfinder.nz_address_metadataGet NZ Address Metadata
- addressfinder.nz_location_metadataGet NZ Location Metadata
- addressfinder.email_verification_apiEmail Verification API
- addressfinder.phone_verification_apiPhone Verification API
- addressfinder.au_address_verificationAU Address Verification
- addressfinder.nz_address_autocompleteNZ Address Autocomplete
- addressfinder.nz_poi_autocomplete_apiNZ POI Autocomplete
- addressfinder.au_location_metadata_apiGet AU Location Metadata
- addressfinder.int_address_metadata_apiGet International Address Metadata
- addressfinder.nz_location_autocompleteNZ Location Autocomplete
- addressfinder.nz_address_reverse_geocodeNZ Address Reverse Geocode
- addressfinder.au_address_autocomplete_apiAU Address Autocomplete
- addressfinder.nz_address_verification_apiNZ Address Verification
- addressfinder.au_location_autocomplete_apiAU Location Autocomplete
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Addressfinder in three steps.
- 01Your users connect AddressfinderThey add their Addressfinder api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “get NZ POI Metadata” can wait for the user to approve.
- 03Any agent can actYour agent calls Addressfinder through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('addressfinder', { read: 'allow', write: 'ask', // nzpoi_metadata_api destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Addressfinder connects.
Users add their Addressfinder api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Addressfinder connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Addressfinder from any agent.
Addressfinder and Arc0, answered.
Can I use Addressfinder with Claude, ChatGPT or Cursor?
Yes. Connect Addressfinder to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Addressfinder actions you allow.
How do users connect Addressfinder?
Users add their Addressfinder api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Addressfinder actions can my agent take?
17 in total: 0 read, 17 write and 0 destructive, such as “get NZ POI Metadata”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Addressfinder?
Yes. Allow read actions and deny writes in the Addressfinder policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Addressfinder too?
Yes. The same Addressfinder connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Addressfinder into your agent.
Your users connect Addressfinder once, under your brand. Your agent gets 17 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan