IP2Location.io provides fast and accurate IP geolocation data, including country, city, ISP, latitude, longitude, and more, supporting both IPv4 and IPv6 lookups.
IP2Location.io provides fast and accurate IP geolocation data, including country, city, ISP, latitude, longitude, and more, supporting both IPv4 and IPv6 lookups. On Nagent, Ip2Location is exposed as a fully-configurable developer tools integration that any agent can call — 8 actions, and API key authentication. No code is required to wire Ip2Location into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ip2Location 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 Ip2Location 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 Ip2Location, with input parameters and output schema. Drop these into any step of an agent built in Helix.
IP2LOCATION_BULK_IP_GEOLOCATIONRetrieve geolocation information for multiple IP addresses in a single request. Supports batch processing of 1-1000 IPv4 or IPv6 addresses with flexible output formats (JSON or CSV) and customizable field selection. Returns comprehensive data including country, region, city, coordinates, timezone, ASN, and proxy detection. Note: Automatically falls back to individual lookups if bulk endpoint is unavailable.
Input parameters
List of IPv4 or IPv6 addresses to look up (1 to 1000 entries).
Optional subset of fields to return; if omitted, all fields are returned.
Response format: 'json' for structured data or 'csv' for raw CSV text.
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
IP2LOCATION_CHECK_CREDITSTool to check remaining IP2Location API credits. Use after setting up authentication to monitor usage.
Input parameters
API key for IP2Location; if omitted, uses the metadata-configured key.
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
IP2LOCATION_DISTANCECalculate the great-circle distance between two IP addresses based on their geographic locations. This tool looks up the geolocation (latitude/longitude) for each IP address and calculates the shortest distance between them over the Earth's surface using the Haversine formula. Supports both IPv4 and IPv6 addresses. Returns the distance in kilometers along with the coordinates of both IPs. Use when you need to determine geographic separation between two IP addresses, such as for latency estimation, geographic analysis, or network optimization.
Input parameters
First IPv4 or IPv6 address
Second IPv4 or IPv6 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
IP2LOCATION_GET_HOSTED_DOMAINSRetrieves a list of domain names hosted on a specific IP address (IPv4 or IPv6). Use this tool when you need to: - Discover which domains are hosted on a particular IP - Investigate shared hosting environments - Analyze domain-to-IP relationships The API supports pagination for IPs with many hosted domains.
Input parameters
IPv4 or IPv6 address to query. Returns a list of domain names that are hosted on this IP address.
IP2WHOIS API key for accessing the Hosted Domains API. Required for authentication.
Page number for pagination (must be >= 1). Use with 'total_pages' in response to retrieve all results. Defaults to 1.
Response format. Accepts 'json' or 'xml'. 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
IP2LOCATION_GET_IP_GEOLOCATIONTool to retrieve geolocation data for an IP address. Use when detailed IP location info is needed.
Input parameters
IPv4 or IPv6 address to look up
Translation language for certain addon fields; valid values as ISO language codes
Extra data to include; valid values: continent, country, region, city, geotargeting, country_groupings, time_zone_info
Response format; default is json
Web service package controlling which fields are returned; valid values WS1–WS25
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
IP2LOCATION_GET_PROXY_DETECTIONTool to detect if an IP is a proxy, VPN, or TOR exit node. Use when verifying anonymizing services.
Input parameters
IPv4 or IPv6 address to check for proxy/VPN/TOR usage
Set to 1 to return only remaining credits instead of lookup data
Level of detail/package (PX1=basic to PX11=full)
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
IP2LOCATION_IP2_WHOIS_DOMAIN_WHOISTool to retrieve WHOIS information for a domain. Use when you need domain registration details.
Input parameters
Domain name to query, e.g. 'example.com'
Response format; either 'json' or 'xml'. 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
IP2LOCATION_LIST_IPSTool to list a curated set of test IPv4 and IPv6 addresses. Use when sample IPs are needed for IP2Location or IP2Proxy lookups during development or testing.
Input parameters
IP version filter: 'ipv4', 'ipv6', or 'all' to return both.
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 72 agents privately built on Nagent that already use Ip2Location.
Build on Nagent
Connect Ip2Location 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 Ip2Location, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ip2Location is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ip2Location is connected, you configure its 8 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ip2Location 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 Ip2Location event fires, the agent kicks off automatically.
Every Ip2Location 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 Ip2Location ships with 8 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ip2Location together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ip2Location-based workflows tailored to your business.