Radar is a full-stack location infrastructure platform offering SDKs and APIs for geofencing, location tracking, geocoding, search, routing, and maps.
Radar is a full-stack location infrastructure platform offering SDKs and APIs for geofencing, location tracking, geocoding, search, routing, and maps. On Nagent, Radar is exposed as a fully-configurable developer tools integration that any agent can call — 37 actions, and API key authentication. No code is required to wire Radar into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Radar to automate the kinds of tasks developer tools 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 Radar 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 Radar, with input parameters and output schema. Drop these into any step of an agent built in Helix.
RADAR_AUTOCOMPLETE_ADDRESS_OR_PLACETool to autocomplete partial addresses and place names based on relevance and proximity. Use after a user inputs a partial address/place to get suggestions, optionally biased by location.
Input parameters
Coordinate bias as 'lat,lng'
Maximum number of results to return (1-100)
Partial address or place to autocomplete
Result types to return (e.g., \['address','place'\])
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
RADAR_CREATE_BEACONTool to create a new beacon in Radar. Use when you need to register a physical beacon device (iBeacon or Eddystone) for location tracking.
Input parameters
A group or category for the beacon (e.g., 'store-entrance', 'parking-lot')
The type of beacon technology
For iBeacon, the UUID identifier
For iBeacon, the major value
For iBeacon, the minor value
Whether the beacon is enabled. If not specified, defaults to true.
Optional custom metadata key-value pairs for the beacon
An external ID for the beacon, used to reference it in your system
The approximate location of the beacon in \[longitude, latitude\] format. Used to sync nearby beacons (within 1 kilometer) to the SDK.
A description for the beacon
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
RADAR_CREATE_TRIPTool to create a new trip. Use after gathering origin and destination details to start tracking a trip.
Input parameters
Mode of travel, one of 'car', 'foot', or 'bike'
Custom key-value pairs for trip
External ID for the trip
Origin location as GeoJSON Point
Tag of origin geofence (e.g. warehouse)
Destination location as GeoJSON Point
Distance threshold in meters for approaching status
Tag of destination geofence (e.g. store)
External ID of origin geofence
External ID of destination geofence
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
RADAR_DELETE_BEACONTool to delete a beacon by its Radar ID. Use when supplying a beacon's unique identifier to remove it.
Input parameters
The Radar _id of the beacon to delete
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
RADAR_DELETE_GEOFENCETool to delete a geofence by ID. Use when supplying a geofence’s unique identifier to remove it.
Input parameters
Unique ID of the geofence to delete
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
RADAR_DELETE_GEOFENCE_BY_TAGTool to delete a geofence by tag and external ID. Use when you have both the tag and external identifier to remove a specific geofence.
Input parameters
The tag of the geofence to delete
The external ID of the geofence to delete
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
RADAR_DELETE_TRIPTool to delete a trip by its Radar ID or external ID. Use after confirming the trip exists.
Input parameters
The unique identifier of the trip to delete. Can be Radar _id or externalId.
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
RADAR_DELETE_USERTool to delete a user by Radar _id, userId, or deviceId. Use after confirming the user identifier exists.
Input parameters
The user identifier - can be Radar _id, userId, or deviceId.
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
RADAR_FORWARD_GEOCODETool to convert an address into geographic coordinates. Use when you have a full address string and need precise latitude/longitude before further location analysis.
Input parameters
Maximum number of results to return (default 10, max 100)
The full address or query string to geocode
Place types to filter results, comma-separated (e.g., 'address','locality')
Two-letter ISO 3166-1 alpha-2 country code to filter results
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
RADAR_GET_BEACONTool to retrieve a beacon by Radar _id. Use when you need to fetch full details of an existing beacon.
Input parameters
The Radar-generated _id of the beacon to retrieve.
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
RADAR_GET_BEACON_BY_TAGTool to get a specific beacon by tag and external ID. Use when you need to retrieve details of a beacon identified by its tag group and external ID.
Input parameters
A group for the beacon (required)
An external ID for the beacon (required)
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
RADAR_GET_CONTEXT_FOR_LOCATIONTool to retrieve context for a given location. Use when you need geofences, place, and region information based on coordinates. Use after obtaining valid latitude and longitude.
Input parameters
Latitude in decimal degrees, between -90 and 90
Longitude in decimal degrees, between -180 and 180
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
RADAR_GET_GEOFENCETool to retrieve a geofence by Radar _id or tag/externalId. Use when you need to fetch full details of an existing geofence.
Input parameters
Unique Radar geofence identifier (e.g., '56db1f4613012711002229f5'). Use this OR tag+externalId.
Tag of the geofence. Must be used together with externalId.
External identifier of the geofence. Must be used together with tag.
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
RADAR_GET_PLACES_SETTINGSTool to retrieve current Places settings for your Radar project. Use when you need to inspect chain detection, supported countries, external ID requirements, and other Places metadata.
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
RADAR_GET_ROUTE_DIRECTIONSTool to get turn-by-turn directions between multiple locations. Use when you need detailed navigation instructions with steps, distances, and durations for routing.
Input parameters
Result language. Options: 'de', 'en', 'es', 'fr', 'ja', 'ko', 'pt', 'ru'. Defaults to 'en'
Travel method. Options: 'car', 'truck', 'foot', 'bike'. Defaults to 'car'
Route features to bypass, comma-separated. Options: 'tolls', 'highways', 'ferries', 'borderCrossings'
Distance units. Options: 'metric', 'imperial'. Defaults to 'imperial'
Initial travel direction in degrees (0=north, 90=east, 180=south, 270=west)
Response geometry format. Options: 'linestring', 'polyline5', 'polyline6'. Defaults to 'polyline6'
A list of up to 25 coordinates to visit in order. A pipe-delimited string in the format 'latitude0,longitude0\\ | latitude1,longitude1\\ | ...'
Return alternative routes (only works for two-location routes). Defaults to false
ISO 8601 datetime for historical traffic consideration (e.g., '2025-01-01T14:30:00Z')
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
RADAR_GET_ROUTE_MATRIXTool to calculate travel distance and duration between multiple origins and destinations for up to 625 routes. Use when you need to compute route metrics for multiple origin-destination pairs efficiently.
Input parameters
Travel mode for route calculation
Unit system for distance measurements (metric returns meters, imperial returns feet)
Pipe-separated list of origin coordinates as 'lat,lon\\ | lat,lon' (e.g., '40.7128,-74.0060\\|37.7749,-122.4194')
Pipe-separated list of destination coordinates as 'lat,lon\\ | lat,lon' (e.g., '40.7589,-73.9851\\|34.0522,-118.2437')
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
RADAR_GET_TRIPTool to retrieve a trip by ID or externalId. Use when you have a trip ID or externalId to fetch its details.
Input parameters
The Radar trip ID or externalId.
Set to 'externalId' when using an external trip ID.
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
RADAR_GET_USERTool to get a user by Radar _id, userId, or deviceId. Returns the user with all location and context data including geofences, places, beacons, and trip information.
Input parameters
User identifier - can be Radar _id, userId, or deviceId
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
RADAR_GET_USERS_IN_GEOFENCETool to retrieve users currently within a specific geofence. Use when you need to list all users inside a geofence by its tag and external ID.
Input parameters
Tag of the geofence
Maximum number of users to return (default: 100, max: 500)
Pagination cursor to fetch the next page of results
External ID of the geofence
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
RADAR_IP_GEOCODETool to geocode an IP address to city, state, and country. Use when you need location details based on an IP address.
Input parameters
The IP address to geocode; defaults to the requester's IP if omitted
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
RADAR_LIST_EVENTSTool to list events. Use when you need to retrieve a paginated list of events with optional filtering.
Input parameters
Return events created before this ISO 8601 timestamp
Filter events by event type
Maximum number of events to return (1-500)
Return events created after this ISO 8601 timestamp
Filter events by user ID
Cursor to return events created after this event ID
Cursor to return events created before this event ID
Filter events by device ID
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
RADAR_LIST_GEOFENCESTool to list all geofences sorted by updated time. Use when you need an overview of all configured geofences.
Input parameters
Filter geofences by tag
Page number to return (default 1)
Maximum number of geofences to return (1-500)
Filter geofences by metadata key-value pairs
Filter geofences by external ID
Return geofences created after this ISO8601 timestamp
Return geofences updated after this ISO8601 timestamp
Return geofences created before this ISO8601 timestamp
Return geofences updated before this ISO8601 timestamp
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
RADAR_LIST_TRIPSTool to list all trips, sorted by updated time. Use when you need to page through the latest trips.
Input parameters
Maximum number of trips to return (1–100). Defaults to 100 when omitted.
Filter trips by Radar user ID.
Filter trips by metadata key/value pairs.
Filter trips by external ID.
Return trips ending immediately before this trip ID.
Return trips starting immediately after this trip ID.
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
RADAR_LIST_USERSTool to list Radar users sorted by update time. Use when you need to page through users in your project.
Input parameters
Only return users who have all of these tags
Maximum number of users to return
User ID after which to return users for pagination
Only return users created after this ISO 8601 timestamp
Only return users updated after this ISO 8601 timestamp
Only return users created before this ISO 8601 timestamp
Only return users updated before this ISO 8601 timestamp
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
RADAR_REVERSE_GEOCODETool to convert geographic coordinates to structured addresses. Use when you have latitude/longitude and need a human-readable address.
Input parameters
Maximum number of results to return (default 1, max 10)
Place types to restrict results, comma-separated (e.g., \['address','place'\])
Two-letter ISO 3166-1 alpha-2 country code to filter results
Latitude and longitude in 'lat,lon' format
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
RADAR_ROUTE_DISTANCETool to compute distance and travel time between origins and destinations. Use when you need route metrics before optimizing or timing routes.
Input parameters
Routing mode
Route features to avoid, comma-separated (e.g., 'tolls,ferries')
Units for distance measurement
Origin coordinate as 'latitude,longitude'
Format for route geometry in response. Options: 'polyline', 'polyline5', 'polyline6', 'linestring'
Destination coordinate as 'latitude,longitude'
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
RADAR_SEARCH_GEOFENCES_NEAR_LOCATIONTool to search for geofences near a given location. Use when you need to find geofences within a radius of specified coordinates.
Input parameters
Filter geofences by these tags
Search radius in meters (default 1000, max 10000)
Latitude of the location to search near
Filter geofences by metadata key-value pairs
Longitude of the location to search near
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
RADAR_SEARCH_PLACES_NEAR_LOCATIONTool to search for places near given coordinates. Use when you need to find points of interest around a location.
Input parameters
Coordinates to search near in 'lat,lng' format
Filter by brand name or ID
Number of results to return; max 100; defaults to 10
Filter by chain IDs
Filter by custom group names
Search radius in meters; max 10000 (10 km); defaults to 1000
ISO 3166-1 alpha-2 country code
Filter by category names
If true, includes chain metadata in each place object
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
RADAR_SEARCH_USERS_NEAR_LOCATIONTool to search for users near a location. Use after obtaining coordinates when you need to retrieve users within a given radius.
Input parameters
Maximum number of users to return (default: 100, max: 500).
Maximum distance in meters to search (default: 1000, range: 1-10000).
Latitude of the location in decimal degrees.
Longitude of the location in decimal degrees.
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
RADAR_TRACK_LOCATION_UPDATETool to track a user's location update. Use when sending a location update for a user, creating or updating user and event data.
Input parameters
Stable unique identifier for logged-in users. Combined with deviceId for user identification.
Whether the user is stopped (not moving)
Accuracy of the location in meters. Must be greater than 0.
Altitude of the device in meters
Unique identifier for the user's device. Required for user identification.
Operating system version of the device
Latitude of the location in degrees
Arbitrary metadata to associate with this track event (up to 32 keys)
Whether this location update is historical (replayed)
Longitude of the location in degrees
ISO 8601 timestamp for historical track events
Manufacturer of the device
Type of device: iOS, Android, or Web
Whether the client is in the foreground
Text description of the user to display on the dashboard
Model of the device
Vertical accuracy of the altitude in meters
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
RADAR_UPDATE_PLACES_SETTINGSTool to update Places settings for your Radar project including chain metadata preferences. Use when you need to configure chain detection or other Places settings.
Input parameters
Chain metadata preferences for Places.
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
RADAR_UPDATE_TRIPTool to update a trip. Use when you need to modify mode, destination, schedule, or active status.
Input parameters
The Radar trip ID or externalId to update
Mode of travel (valid values: car, foot, bike, truck, motorbike)
Whether the trip is active (true) or paused/completed (false)
Set to 'externalId' when the provided ID is an external trip ID
Custom metadata (max 16 key-value pairs)
New external ID for the trip
Explicit destination coordinates if not using a geofence.
Threshold in meters for the 'arrived' state
Scheduled arrival time in ISO8601 format
Threshold in meters for the 'approaching' state
Tag of destination geofence
Radius in meters for the destination geofence
External ID of destination geofence
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
RADAR_UPDATE_TRIP_BY_IDTool to update a trip status by Radar _id or external ID. Use when you need to change trip status to started, approaching, arrived, completed, or canceled.
Input parameters
Trip ID (Radar _id or externalId) to update
The new status of the trip
Optional custom key-value pairs for the trip
Optional stable unique ID for the trip
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
RADAR_UPSERT_BEACON_BY_IDTool to create or update a beacon by Radar _id. Use when you need to ensure a beacon with a specific ID exists with updated properties.
Input parameters
The Radar beacon _id to create or update
A group for the beacon
Beacon type, must be 'ibeacon'
The iBeacon UUID
Major number for the beacon (can be string or integer)
Minor number for the beacon (can be string or integer)
If true, the beacon will generate events; defaults to true
External ID for the beacon
The approximate location in \[longitude, latitude\] format
Display name for the beacon
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
RADAR_UPSERT_BEACON_BY_TAGTool to create or update a beacon by tag and externalId. Use when you need to ensure a beacon exists or is updated with specific identifiers.
Input parameters
Tag identifier for grouping the beacon (appears in URL path)
UID identifier for Eddystone beacons (required for eddystone, not used for ibeacon)
Beacon technology type: ibeacon or eddystone
UUID identifier for iBeacon type (required for ibeacon, not used for eddystone)
Major ID for iBeacon type (required for ibeacon, not used for eddystone)
Minor ID for iBeacon type (required for ibeacon, not used for eddystone)
Whether the beacon is active and generates events
Instance ID for Eddystone beacons (required for eddystone, not used for ibeacon)
Custom key-value pairs for the beacon (max 16 keys, values must be string/boolean/number)
External identifier mapping to your database (appears in URL path)
Beacon location as \[longitude, latitude\] in GeoJSON format
Human-readable display name for the beacon
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
RADAR_UPSERT_GEOFENCETool to create or update a geofence by tag and externalId. Use when ensuring a geofence exists or is updated based on identifiers.
Input parameters
Tag of the geofence to create or update
Shape type of the geofence
Radius in meters defining a circle. Required when type='circle'.
GeoJSON geometry object for the geofence
Custom key-value pairs attached to the geofence
External identifier of the geofence
Array of \[longitude, latitude\] pairs defining a polygon. Required when type='polygon'.
Human-readable description of the geofence (required by the API)
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
RADAR_UPSERT_GEOFENCE_BY_IDTool to create or update a geofence by Radar _id. Use when you need to upsert a geofence using its internal Radar identifier.
Input parameters
Radar internal geofence _id to create or update
Group identifier for the geofence
Geofence geometry type: circle, polygon, or isochrone
Distance in meters (required for circle and isochrone types)
Boolean to enable/disable event generation for this geofence
Custom key-value pairs (up to 16 keys)
External database reference
Location data in \[longitude, latitude\] format for circle/isochrone, or array of coordinate pairs for polygon
A display name for the geofence (required by API)
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 42 agents privately built on Nagent that already use Radar.
Build on Nagent
Connect Radar 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 Radar, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Radar is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Radar is connected, you configure its 37 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Radar 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 Radar event fires, the agent kicks off automatically.
Every Radar 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 Radar ships with 37 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Radar together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Radar-based workflows tailored to your business.