Placekey standardizes location data by assigning unique IDs to physical addresses, simplifying address matching and enabling data sharing across platforms
Placekey standardizes location data by assigning unique IDs to physical addresses, simplifying address matching and enabling data sharing across platforms On Nagent, Placekey is exposed as a fully-configurable analytics integration that any agent can call — 4 actions, and API key authentication. No code is required to wire Placekey into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Placekey to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Placekey into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Placekey, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PLACEKEY_GET_GEOCODE_FROM_ADDRESSThis tool retrieves geocode information (latitude and longitude) for a given address using the Placekey API. It accepts address components (street_address, city, region, postal_code, iso_country_code) and returns geocode data including the unique Placekey identifier and location details.
Input parameters
City name
State/region code
Postal/ZIP code
Street address of the location
Two-letter country code
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLACEKEY_GET_PLACEKEYTool to get a Placekey for a single location using address, coordinates, or POI details. Use when you need to obtain a unique identifier for a physical place with support for address fields, coordinates, location name, and optional metadata for enhanced matching.
Input parameters
The city where the place is located
The second-level administrative region (e.g., state in US)
Options to customize the response and matching behavior
The latitude of the place in WGS-84 coordinates
Custom identifier for this query. Will be echoed back in the response.
The longitude of the place in WGS-84 coordinates
The postal code for the place
The name of the place or business (POI name) for better matching
Additional metadata about the place to improve matching accuracy
The street address of the place
The ISO 2-letter country code (e.g., US, CA, GB)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLACEKEY_GET_PLACEKEY_FROM_ADDRESSConvert a physical address into a unique Placekey identifier. The Placekey is a universal standard identifier for any physical place that helps in location matching, enrichment, and deduplication.
Input parameters
The city name
The state/region code (e.g., 'CA' for California)
The postal/ZIP code
Name of the location/business if available
The street address of the location
The two-letter ISO country code (e.g., 'US' for United States)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLACEKEY_GET_PLACEKEYS_BULKGet Placekeys for multiple locations in bulk (up to 100 queries per request). All queries must have the same iso_country_code. Supports address, coordinates, and POI queries with optional query_id for tracking. Returns an array of Placekey results for each query.
Input parameters
Options to customize the Placekey response
Array of location queries. Maximum 100 queries per request. All queries must have the same iso_country_code.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 66 agents privately built on Nagent that already use Placekey.
Build on Nagent
Connect Placekey to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Placekey, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Placekey is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Placekey is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Placekey steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Placekey event fires, the agent kicks off automatically.
Every Placekey action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Placekey ships with 4 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Placekey together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Placekey-based workflows tailored to your business.