Placekey MCP integration for AI agents.
Connect AI agents to Placekey through 4 structured actions, including get geocode from address, get placekey, and get placekey from address. Review authentic…
- ACTION CONTRACTS
- 4
- 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 Placekey integration exposes
The Placekey Agent App exposes 4 provider-backed actions for location and data work. Its current contract lets an authorized agent resolve a postal address with placekey and return the matched geocode response for the location, look up a single location with placekey and return its placekey identifier plus optional enrichment fields, and resolve a postal address into a placekey identifier using the placekey single-lookup api. 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 Placekey account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Placekey capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_geocode_from_addressREADResolve a postal address with Placekey and return the matched geocode response for the location.
INPUTS: street_address / city / region / postal_code / iso_country_code
get_placekeyREADLook up a single location with Placekey and return its Placekey identifier plus optional enrichment fields.
INPUTS: query_id / street_address / city / region / postal_code
get_placekey_from_addressREADResolve a postal address into a Placekey identifier using the Placekey single-lookup API.
INPUTS: street_address / city / region / postal_code / iso_country_code
get_placekeys_bulkREADLook up up to 100 locations in one Placekey bulk request and return the result for each query item.
INPUTS: queries / options
INPUT CONTRACTS
Know what the action needs before it runs.
get_geocode_from_address
street_addressREQUIRED- The street address of the location to resolve into a Placekey.
cityOPTIONAL- The city of the location.
regionREQUIRED- The region or state of the location.
postal_codeOPTIONAL- The postal code of the location.
iso_country_codeREQUIRED- The ISO 3166-1 alpha-2 country code for the queried location.
get_placekey
query_idOPTIONAL- A custom identifier echoed back in the Placekey response.
street_addressOPTIONAL- The street address of the location to resolve.
cityOPTIONAL- The city of the queried location.
regionOPTIONAL- The second-level administrative region, such as a US state code.
postal_codeOPTIONAL- The postal code of the queried location.
get_placekey_from_address
street_addressREQUIRED- The street address of the location to resolve into a Placekey.
cityOPTIONAL- The city of the location.
regionREQUIRED- The region or state of the location.
postal_codeOPTIONAL- The postal code of the location.
iso_country_codeREQUIRED- The ISO 3166-1 alpha-2 country code for the queried location.
get_placekeys_bulk
queriesREQUIRED- The list of location queries to resolve with Placekey.
optionsOPTIONAL- Options that customize the Placekey lookup response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Geocode From Address
Resolve a postal address with Placekey and return the matched geocode response for the location. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_geocode_from_addressVerify with Get Placekey
Look up a single location with Placekey and return its Placekey identifier plus optional enrichment fields. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_placekeySAFETY BOUNDARY
Operate Placekey with explicit limits
- Authorize Placekey with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Placekey 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 Placekey rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Placekey task completed successfully.
CONNECTION MODEL
API key
Placekey API key used with the apikey request header. Generate it from the Placekey Developer Portal dashboard: https://docs.placekey.io/documentation/api-overview/authentication.
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
- 4
- 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 Placekey.