AddressZen MCP integration for AI agents.
Connect AI agents to AddressZen through 3 structured actions, including find address, get key availability, and retrieve address usa. Review authentication…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the AddressZen integration exposes
The AddressZen Agent App exposes 3 provider-backed actions for location and data work. Its current contract lets an authorized agent autocomplete addresses from a partial query and return the official addresszen suggestions, retrieve the current addresszen key availability and context list, and retrieve a usa-formatted address from an addresszen suggestion identifier and return the official response wrapper. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected AddressZen account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AddressZen capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_addressREADAutocomplete addresses from a partial query and return the official AddressZen suggestions.
INPUTS: query / context / country / limit
get_key_availabilityREADRetrieve the current AddressZen key availability and context list.
retrieve_address_usaREADRetrieve a USA-formatted address from an AddressZen suggestion identifier and return the official response wrapper.
INPUTS: address
INPUT CONTRACTS
Know what the action needs before it runs.
find_address
queryREQUIRED- The partial address string to autocomplete.
contextOPTIONAL- The optional AddressZen context used to narrow the search.
countryOPTIONAL- The optional country name used to filter results.
limitOPTIONAL- The maximum number of suggestions to return.
retrieve_address_usa
addressREQUIRED- The suggestion identifier returned by the AddressZen autocomplete API.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Address
Autocomplete addresses from a partial query and return the official AddressZen suggestions. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_addressVerify with Get Key Availability
Retrieve the current AddressZen key availability and context list. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_key_availabilitySAFETY BOUNDARY
Operate AddressZen with explicit limits
- Authorize AddressZen with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned AddressZen data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in AddressZen rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AddressZen task completed successfully.
CONNECTION MODEL
API key
AddressZen API key used as the api_key query parameter. Find or create it from your AddressZen dashboard: https://docs.addresszen.com/docs/guides/api-key
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by AddressZen.