Geoapify offers a suite of APIs for integrating maps, geocoding, routing, and other location-based services into applications.
Geoapify offers a suite of APIs for integrating maps, geocoding, routing, and other location-based services into applications. On Nagent, Geoapify is exposed as a fully-configurable developer tools integration that any agent can call — 25 actions, and API key authentication. No code is required to wire Geoapify into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Geoapify 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 Geoapify 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 Geoapify, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GEOAPIFY_ADDRESS_AUTOCOMPLETETool to fetch address suggestions based on partial input. Use when you need to get predictive suggestions from incomplete address text.
Input parameters
Bias results by proximity or boundary using formats: proximity:lon,lat\\ | circle:lon,lat,radius\\ | rect:lon1,lat1,lon2,lat2\\ | countrycode:CC; combine with '\\ | ' for OR
Language code (ISO 639-1, 2 letters, e.g., 'en')
Partial address text to autocomplete
Restrict suggestions by location type
Maximum number of results to return, must be >= 1
Filter results by boundary or country using formats: circle:lon,lat,radius\\ | rect:lon1,lat1,lon2,lat2\\ | countrycode:CC\\ | place:placeId; combine with '\\ | ' for AND
Response format; one of: 'geojson' (default), 'json', 'xml'
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
GEOAPIFY_BATCH_REQUESTSCreate or retrieve asynchronous batch processing jobs for geocoding, reverse geocoding, routing, or isoline APIs. Use cases: - Batch geocode up to 1000 addresses at once (forward geocoding) - Batch reverse geocode multiple coordinates - Process multiple routing or isoline requests in one batch Workflow: 1. Create a job by providing 'api' and 'inputs' (returns job ID and status 'pending') 2. Poll the job by providing 'id' until status changes from 'pending' to complete (results available)
Input parameters
32-character hex job ID to retrieve status/results. Omit to create a new job. When provided, all other fields must be omitted.
API endpoint to batch. Required when creating a job. /v1/geocode/search for forward geocoding, /v1/geocode/reverse for reverse geocoding, /v1/routing for routes, /v1/isoline for isochrones/isodistances.
Common JSON body applied to all inputs (for APIs requiring a body). Input-level body values override these.
Array of 1-1000 input objects. Required when creating a job. Each input has 'params' (required) and optional 'id' and 'body'.
Common query parameters applied to all inputs. E.g., {'lang': 'en', 'limit': '3'}. Input-level params override these.
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
GEOAPIFY_BOUNDARIESRetrieve all administrative boundaries that contain a given location. Returns hierarchical boundaries (suburb, city, county, state, country) as GeoJSON features. Use this to find what administrative areas a coordinate belongs to, get boundary polygons for mapping, or identify postal codes and political districts for a location.
Input parameters
Geoapify Place ID (from Places, Geocoding, or Geometry API responses). Use this OR lat/lon, not both.
Latitude of the location (-90 to 90). Required together with lon if id is not provided.
Longitude of the location (-180 to 180). Required together with lat if id is not provided.
ISO 639-1 two-letter language code for localized names (e.g., 'en', 'de', 'fr', 'es', 'ja'). Results will use local names if not specified.
Geometry detail level: 'point' returns centroid only (fastest), 'geometry_1000/5000/10000' returns simplified polygon boundaries at 1km/5km/10km resolution (lower = more detailed, larger response).
Type of boundary to retrieve: 'administrative' for government divisions (city/county/state/country), 'postal_code' for postal zones, 'political' for electoral districts, 'low_emission_zone' for environmental zones.
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
GEOAPIFY_CREATE_BATCH_FORWARD_GEOCODE_JOBTool to create a batch forward geocoding job for up to 1000 addresses. Use when you need to geocode multiple addresses asynchronously. Returns a job ID for retrieving results once processing is complete.
Input parameters
Prioritize results based on proximity to geographic areas without limiting search scope. Formats: 'circle:lon,lat,radiusMeters' (circular priority), 'rect:lon1,lat1,lon2,lat2' (rectangular priority), 'countrycode:code1,code2' (country priority, use 'auto' for IP detection), 'proximity:lon,lat' (prioritize by distance from point).
Result language in ISO 639-1 format (e.g., 'en' for English).
Location types for filtering geocoding results.
Refine geocoding results by applying geographic filters. Formats: 'circle:lon,lat,radiusMeters' (circular area), 'rect:lon1,lat1,lon2,lat2' (rectangular area), 'countrycode:code1,code2' (specific countries, use 'auto' for IP detection), 'place:placeId' (specific boundary using place_id).
List of address strings to geocode (1-1000 addresses). Each item should be a valid address or partial address.
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
GEOAPIFY_CREATE_BATCH_REVERSE_GEOCODE_JOBTool to create a batch reverse geocoding job that converts multiple lat/lon coordinates into addresses asynchronously. Use when you need to reverse geocode multiple coordinates (up to 1000) in one request. Returns a job ID for retrieving results.
Input parameters
Result language in ISO 639-1 format (2-letter code, e.g., 'en' for English, 'de' for German).
Location type to search for. Filters results by type: country, state, city, postcode, street, or amenity (POIs).
List of latitude/longitude coordinate pairs to reverse geocode. Minimum 1, maximum 1000 locations.
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
GEOAPIFY_FORWARD_GEOCODINGTool to convert an address into geographic coordinates. Use when you need latitude and longitude from an address.
Input parameters
Location bias. Formats: 'circle:lon,lat,radiusMeters', 'rect:lon1,lat1,lon2,lat2', 'countrycode:code1,code2', 'proximity:lon,lat'. Combine multiple with '\\ | ' for OR logic. Default is countrycode:auto.
City name for structured address search
Result language (ISO 639-1 2-letter code, e.g., 'en')
Amenity or place name for structured address search
Free-form address to search, e.g., 'Berlin, Germany'
Location type filter. Allowed: country, state, city, postcode, street, amenity, locality
Maximum number of results to return (default 5)
State or province for structured address search
Geoapify API key (auto-injected from authentication, typically not needed)
Location filters. Formats: 'circle:lon,lat,radiusMeters', 'rect:lon1,lat1,lon2,lat2', 'countrycode:code1,code2', 'place:placeId'. Combine multiple with '\\ | ' for AND logic.
Response format. One of: geojson (default), json, xml
Street name for structured address search
Country name for structured address search
Postal code or ZIP for structured address search
House number for structured address search
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
GEOAPIFY_GEOMETRYTool to perform geometric operations on stored polygon geometries. Use when combining or intersecting multiple stored geometries.
Input parameters
List of at least two geometry IDs to combine or intersect.
Geometric operation to apply. Must be 'union' or 'intersection'.
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
GEOAPIFY_GET_BATCH_FORWARD_GEOCODE_RESULTSTool to retrieve batch forward geocoding job results using the job ID. Use when you need to fetch geocoded addresses from a previously submitted batch job. Results available in JSON or CSV format. Job must be complete (status 200) to get results.
Input parameters
The unique job ID that was returned when the batch geocoding job was created. This ID is used to retrieve the results.
The format in which to retrieve the results, either JSON or CSV. Defaults to JSON.
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
GEOAPIFY_GET_BATCH_REVERSE_GEOCODE_RESULTSTool to retrieve batch reverse geocoding job results. Use when you have a batch job ID from creating a batch reverse geocoding job and want to fetch the completed results.
Input parameters
The unique job ID that was returned when the batch reverse geocoding job was created. This ID is used to retrieve the results.
The format in which to retrieve the results, either JSON or CSV. Defaults to JSON if not specified.
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
GEOAPIFY_GET_BOUNDARIES_CONSISTS_OFGet boundaries that a specified location consists of. Returns child administrative divisions (states for country, districts for city). Useful for drilling down into sub-regions.
Input parameters
Geoapify Place ID of the parent boundary to get sub-boundaries for (e.g., states for a country, districts for a city). Obtain this ID from Geocoding, Places, or other Boundaries API responses.
ISO 639-1 two-letter language code for localized names (e.g., 'en', 'de', 'fr', 'es', 'ja'). Results will use local names if not specified.
Geometry detail level: 'point' returns centroid only (fastest), 'geometry_1000/5000/10000' returns simplified polygon boundaries at 1km/5km/10km resolution (lower = more detailed, larger response, higher cost).
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
GEOAPIFY_GET_MAP_STYLETool to retrieve vector map style JSON for MapLibre GL and Mapbox GL. Returns a Mapbox-compatible style specification for rendering vector tiles.
Input parameters
Map style name. Common styles: osm-carto (OpenStreetMap default), osm-bright (bright OSM), dark-matter (dark theme), positron (light theme), toner (high contrast).
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
GEOAPIFY_GET_STATIC_MAPTool to generate static map images with customizable style, size, center, zoom, markers, and geometries. Use when you need a map image for display or printing.
Input parameters
Bounding box to fit the map view in format 'rect:lon1,lat1,lon2,lat2'. The map automatically adjusts center and zoom to fit this area. Cannot be used with center/zoom.
Map zoom level (0-20). Higher values show more detail. Required when using center parameter.
Map style to use. Options: osm-carto (OpenStreetMap Carto), osm-bright (OSM Bright), positron (light base map), dark-matter (dark base map), and others.
Image width in pixels (1-4096). For high-resolution images with scaleFactor > 1, the effective width should not exceed 4096 pixels.
Map center coordinates in format 'lonlat:longitude,latitude' (e.g., 'lonlat:2.3522,48.8566' for Paris). Required unless area, marker, geometry, or geojson is specified.
Output image format. Options: 'png' (default, supports transparency), 'jpeg' (smaller file size).
Image height in pixels (1-4096). For high-resolution images with scaleFactor > 1, the effective height should not exceed 4096 pixels.
Marker definition(s) in format 'lonlat:lon,lat;color:hex;size:small\\ | medium\\ | large;type:awesome\\ | material'. Multiple markers can be separated by '\\ | '. Example: 'lonlat:2.35,48.85;color:#ff0000;size:medium\\ | lonlat:2.36,48.86;color:#0000ff'.
GeoJSON Feature or FeatureCollection (URL-encoded, max 1024 chars). Features can have properties: fillColor, fillOpacity, lineColor, lineWidth, lineOpacity. The map view automatically adjusts to fit the GeoJSON bounds.
Geometry to display on the map (lines, polygons, circles, rectangles). Format: 'type:geometry_definition;color:hex;width:number'. Types: polyline, polygon, circle, rect. Example: 'polyline:2.35,48.85,2.36,48.86,2.37,48.87;color:#0000ff;width:3'.
Resolution multiplier for high-quality/print images (1-8). Default is 1. Use 2 for retina displays. Higher values (up to 8) available for print media.
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
GEOAPIFY_IP_GEOLOCATIONLookup geographic location information for an IP address. Returns city-level location data including country, region, city, coordinates, and additional metadata like currency and language. If no IP is provided, returns location for the caller's IP address.
Input parameters
IP address (IPv4 or IPv6) to lookup; if omitted, uses the caller's IP.
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
GEOAPIFY_ISOLINETool to generate isochrone or isodistance isolines. Use when visualizing reachable areas from a point; use `id` to poll ongoing calculations.
Input parameters
Unique identifier of previously generated isoline (valid 24h). Exclusive with lat/lon/type/mode/range.
Latitude of the origin point in decimal degrees. Required for new calculation.
Longitude of the origin point in decimal degrees. Required for new calculation.
Travel mode for route calculation. Required for new calculation.
Isoline type: 'time' (seconds) or 'distance' (meters). Required for new calculation.
Features to avoid separated by '\\ | '. Options: tolls, ferries, highways. Example: 'tolls\\ | ferries'.
Isoline range(s): seconds for time type (max 3600) or meters for distance type (max 60000). Supply single int or list for multiple ranges.
Units for distance calculations. Default metric.
Traffic model (motorized modes only). Default free_flow.
Vehicle max speed in KPH (10-252). Applies to drive/truck/bus modes.
Route optimization. Default balanced.
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
GEOAPIFY_LIST_POSTCODESTool to list postcodes within a specified area or boundary. Use when you need to retrieve multiple postcodes in a geographic region using filters like circle, rectangle, or place ID.
Input parameters
Maximum number of postcodes to return (1-100)
Filter by area. Supported formats: 'place:place_id' (e.g., 'place:51a59aa36fd7e7594059923ee27e96a94740f00102f90185250300000000c00208'), 'rect:lon1,lat1,lon2,lat2' (e.g., 'rect:-0.1447,51.5008,-0.1108,51.5163'), 'circle:lon,lat,radius_meters' (e.g., 'circle:-0.1278,51.5074,5000')
Restrict results to country (ISO 3166-1 alpha-2 code, e.g., 'gb', 'us')
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
GEOAPIFY_MAP_MATCHINGSnap GPS traces to the road network for accurate route reconstruction. Use this tool to: - Correct GPS drift and inaccuracies in recorded tracks - Align vehicle/cycling/walking traces to actual roads - Get road names and properties along the matched route - Calculate accurate distance and travel time from GPS data
Input parameters
Travel mode: 'drive' for car, 'walk' for pedestrian, or 'bicycle' for cycling
List of GPS waypoints to snap to the road network. Provide at least 2 waypoints (up to 1000).
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
GEOAPIFY_MAP_TILESTool to fetch raster map tiles or style JSON from Geoapify. Use when rendering custom maps with specific styles.
Input parameters
Tile column X (required when mode='tile').
Tile row Y (required when mode='tile').
Zoom level (required when mode='tile').
Choose 'tile' to fetch a raster PNG tile, or 'style' to fetch the style JSON.
Map style ID. E.g., 'osm-bright', 'positron', 'dark-matter'.
Your Geoapify API key.
Whether to request high-DPI '@2x' tile (only when mode='tile').
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
GEOAPIFY_MARKER_ICONGenerate custom map marker icons as PNG images. Creates customizable marker icons for use in mapping applications (Leaflet, MapLibre GL, Google Maps, etc.). Supports multiple styles (material, circle, plain), custom colors, icons from Material Design and Font Awesome libraries, or custom text/numbers. Example use cases: - Create a red location pin with a star icon - Generate numbered markers (1, 2, 3...) for route waypoints - Create custom-colored markers matching your brand
Input parameters
Icon name from the selected library (e.g., 'star', 'home', 'landmark', 'map-marker'). See Material Design Icons or Font Awesome v6 for available names.
Total icon image height in pixels. Common values: 30, 40, 50, 80.
Text or number to display instead of an icon (e.g., '1', 'A', 'B'). Cannot be used with 'icon' parameter.
Marker style/shape type. Options: 'material' (pin-style), 'awesome' (shaped marker), 'circle' (round), 'plain' (icon only, no background). Defaults to 'material'.
Background/marker color as hex code (e.g., '#FF5050', '#3498db'). Not used for type='plain'.
Icon library to use. Options: 'material' (Material Design Icons), 'awesome' (Font Awesome v6), 'lucide' (Lucide icons). Defaults to match 'type' parameter.
Set to true to remove the default shadow from the marker.
Inner icon/text size in pixels. Should be less than 'size'. Common values: 20, 28, 35.
Scale factor for high-resolution displays. Use 2 for retina/HiDPI displays.
Shadow color as hex code (e.g., '#00000080' for semi-transparent black).
Border/stroke color as hex code (e.g., '#000000'). Not used for type='plain'.
Color of inner icon/text as hex code (e.g., '#FFFFFF', '#4f4f4f').
Set to true to remove the white circle background behind the icon.
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
GEOAPIFY_PLACE_DETAILSTool to retrieve detailed information about a specific place. Use when you have a place ID or coordinates and need comprehensive metadata.
Input parameters
Place unique identifier returned by Geoapify Places or Geocoding API. Required if `lat` and `lon` are not provided.
Latitude of the place. Must be provided together with `lon` if `id` is omitted.
Longitude of the place. Must be provided together with `lat` if `id` is omitted.
Response language (ISO 639-1 code, two lowercase letters).
Comma-separated list of features to return. Defaults to `details` when request is by `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
GEOAPIFY_PLACESSearch for points of interest (POIs) like restaurants, hotels, attractions, hospitals, etc. within a geographic area. Use this tool when you need to find places by category near a location. You must provide either a 'filter' (to search within a bounded area) or 'bias' (to rank results by proximity to a point). Common use cases: - Find restaurants near a location: categories=\['catering.restaurant'\], bias='proximity:lon,lat' - Search for hotels in a city area: categories=\['accommodation.hotel'\], filter='circle:lon,lat,5000' - Find wheelchair-accessible attractions: categories=\['tourism.attraction'\], conditions=\['wheelchair'\]
Input parameters
Proximity bias to rank results by distance to a point. Required if 'filter' not provided. Format: 'proximity:lon,lat'. Results are sorted by distance to this point.
ISO 639-1 language code for localized results (e.g., 'en', 'de', 'ja', 'fr').
Filter results to only include places matching this name (case-insensitive partial match).
Maximum number of results to return (1-500). Default is 20.
Spatial filter to constrain search area. Required if 'bias' not provided. Formats: 'circle:lon,lat,radiusMeters' (e.g., 'circle:13.4,52.5,1000' for 1km radius), 'rect:lon1,lat1,lon2,lat2' (bounding box with SW and NE corners).
Number of results to skip for pagination. Use with 'limit' to paginate through results.
Place category keys to search for. Common categories include: 'catering.restaurant', 'catering.cafe', 'accommodation.hotel', 'tourism.attraction', 'tourism.sights', 'healthcare.hospital', 'commercial.supermarket', 'entertainment.cinema', 'sport.fitness'. Multiple categories can be provided to search across types.
Additional condition filters for accessibility or amenities, e.g., 'wheelchair' to filter only wheelchair-accessible places, 'internet_access' for places with WiFi.
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
GEOAPIFY_POSTCODETool to retrieve postcode information for a location. Use when you need to fetch postcode details based on a given postcode or geographic coordinates.
Input parameters
Latitude of location; must be provided with lon
Longitude of location; must be provided with lat
Response language (ISO 639-1 code, 2 letters)
Response format; one of: 'json', 'geojson', 'xml'
Return geometry as 'point' or 'original' boundary
Postal code to search for
Restrict search to country (ISO 3166-1 alpha-2)
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
GEOAPIFY_REVERSE_GEOCODINGTool to reverse geocode coordinates into a structured address. Use when converting lat/lon to human-readable addresses.
Input parameters
Latitude coordinate in decimal degrees.
Longitude coordinate in decimal degrees.
2-letter ISO 639-1 language code for the result.
Address level to search; one of country, state, city, postcode, street, amenity.
Maximum number of results to return (default: 1).
Response format: one of geojson, json, xml (default: geojson).
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
GEOAPIFY_ROUTE_MATRIXTool to compute travel time and distance matrices. Use when you need durations and distances between multiple origin and destination pairs.
Input parameters
Travel mode for the route calculation. Options: 'drive' (default), 'walk', 'bicycle', 'truck', etc.
Route type preference: 'balanced' (default), 'short' (shortest distance), 'less_maneuvers' (fewer turns).
List of road types or features to avoid. Each item specifies a type ('tolls', 'highways', 'ferries', 'unpaved') and optional importance (0.0-1.0).
Unit system for distances: 'metric' (default, meters) or 'imperial' (miles).
Geoapify API key
List of origin waypoints (at least one required). Each waypoint has a location \[longitude, latitude\].
List of destination waypoints (at least one required). Each waypoint has a location \[longitude, latitude\].
Traffic model for motorized modes: 'free_flow' (default, no traffic) or 'approximated' (estimated traffic delays).
Maximum vehicle speed in km/h (10-252). Limits the assumed travel speed.
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
GEOAPIFY_ROUTE_PLANNEROptimize multi-agent routes for deliveries, pickups, and service jobs. Solves Vehicle Routing Problems (VRP) including: Travelling Salesman (TSP), Capacitated VRP, VRP with Time Windows, and Pickup-Delivery problems. Required: Either 'jobs' (one-way tasks) or 'shipments' (pickup-delivery pairs). Coordinates: Use \[longitude, latitude\] format (not lat/lon).
Input parameters
One-way service jobs to assign. Use for simple deliveries/services. Required if shipments not provided.
Travel mode: 'drive' (car), 'truck', 'bicycle', 'walk', 'transit'. Defaults to drive.
Route optimization: 'balanced' (default), 'short' (minimize distance), 'less_maneuvers' (simpler directions).
Roads or features to avoid: tolls, ferries, highways, or specific locations.
Distance units in response: 'metric' (meters) or 'imperial' (miles). Defaults to metric.
List of agents (vehicles/workers) to assign work to. Defaults to 1 agent if omitted.
Traffic model: 'free_flow' (no traffic) or 'approximated' (estimated traffic). Defaults to free_flow.
Reusable locations referenced by index. Useful for warehouses or depots used by multiple agents.
Max speed in km/h to cap travel speed calculations for driving modes.
Paired pickup-delivery shipments. Use when items must be picked up then delivered. Required if jobs not provided.
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
GEOAPIFY_ROUTINGTool to calculate routes between multiple waypoints. Use when you need both distance, time, and turn-by-turn directions for two or more coordinates.
Input parameters
Language code for instructions (e.g., en, de, fr).
Travel mode (default: drive).
Route optimization: balanced (default), short, less_maneuvers. (less_maneuvers only for motorized road modes)
Avoid options separated by '\\ | ', e.g., 'tolls\\ | ferries:0.5\\ | highways'.
Distance units; metric (default) or imperial.
Response format: geojson (default), json, xml.
Comma-separated extra details: instruction_details, route_details, elevation.
Traffic model for motorized modes (default: free_flow).
Max vehicle speed in KPH (10-252).
Two or more waypoints in 'lat,lon' or 'lonlat:lon,lat' format, pipe-separated. E.g. '36.734770,-76.610637\\ | 36.761226,-76.488354'
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 Geoapify.
Build on Nagent
Connect Geoapify 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 Geoapify, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Geoapify is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Geoapify is connected, you configure its 25 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Geoapify 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 Geoapify event fires, the agent kicks off automatically.
Every Geoapify 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 Geoapify ships with 25 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Geoapify together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Geoapify-based workflows tailored to your business.