ipdata provides a simple HTTP-based API that allows you to look up the location, ownership, and threat profile of any IP address.
ipdata provides a simple HTTP-based API that allows you to look up the location, ownership, and threat profile of any IP address. On Nagent, Ipdata.co is exposed as a fully-configurable developer tools integration that any agent can call — 28 actions, and API key authentication. No code is required to wire Ipdata.co into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ipdata.co 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 Ipdata.co 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 Ipdata.co, with input parameters and output schema. Drop these into any step of an agent built in Helix.
IPDATA_CO_ADVANCED_ASN_LOOKUPTool to perform advanced ASN lookup returning prefixes, peers, and registry details. Use after confirming ASN number when detailed ASN info is required.
Input parameters
Autonomous System Number to look up (positive integer, e.g., 2).
Comma-separated list of specific fields to return (e.g., 'name,ipv4_prefixes').
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
IPDATA_CO_EU_LOOKUP_SPECIFIC_IPLookup geolocation, threat intel, and network data for a specific IP address using the EU data residency endpoint. Use this tool when: - You need IP lookup with GDPR compliance (data processed and stored only within EU datacenters) - Looking up any IPv4 or IPv6 address for location, ASN, threat, or company information The EU endpoint (eu-api.ipdata.co) ensures all API requests are routed through EU-based servers in Frankfurt, Paris, and Ireland.
Input parameters
The IPv4 or IPv6 address to look up (e.g., '8.8.8.8' or '2001:4860:4860::8888')
Comma-separated list of response fields to include. Use this to reduce response size if you only need specific data. Available fields: ip, is_eu, city, region, region_code, country_name, country_code, continent_name, continent_code, latitude, longitude, postal, calling_code, flag, emoji_flag, emoji_unicode, asn, company, carrier, languages, currency, time_zone, threat, count
JSONP callback function name for wrapping the response (rarely needed for API use)
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
IPDATA_CO_FIELD_CALLING_CODETool to fetch the international calling_code for an IP's country. Use when you need only the calling code field from ipdata_co.
Input parameters
IPv4 or IPv6 address to lookup. If omitted, the caller's IP address is used.
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
IPDATA_CO_FIELD_CARRIERRetrieve mobile carrier information (name, MCC, MNC) for an IP address. Returns carrier data only for mobile network IPs; non-mobile IPs return null fields.
Input parameters
IPv4 or IPv6 address to query. If omitted, defaults to 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
IPDATA_CO_FIELD_CITYTool to return only city for an IP. Use when only the city name is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_CONTINENT_CODERetrieve the continent code for a given IP address. Returns a two-letter code (AF, AN, AS, EU, NA, OC, SA) indicating which continent the IP is geographically located in. Use this when you only need the continent information without full IP geolocation details.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_CONTINENT_NAMETool to return only continent name for an IP. Use when only the continent name is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_COUNTTool to return only the request count made by your API key in the last 24 hours. Use when monitoring your API usage and you only need the total count.
Input parameters
Optional IPv4 or IPv6 address. The count returned is always your API key's total requests in the last 24 hours, regardless of whether an IP is 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
IPDATA_CO_FIELD_COUNTRY_CODETool to return only country_code for an IP. Use when only the 2-letter country code is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_COUNTRY_NAMEGet the country name for an IP address using ipdata.co geolocation API. Returns only the country name (e.g., 'United States', 'Germany', 'Japan'). Use this lightweight action when you only need the country name without full IP details.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_CURRENCYTool to return only currency object for an IP. Use when currency details are needed.
Input parameters
IPv4 or IPv6 address to query. 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
IPDATA_CO_FIELD_EMOJI_FLAGTool to return only emoji flag for an IP. Use when only the country flag emoji is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_EMOJI_UNICODETool to return only emoji_unicode for an IP. Use when only the Unicode country flag emoji is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_IPRetrieve the public IP address of the calling client. This action calls the IPData API to determine the caller's external/public IP address. It returns only the IP string with no additional geolocation data. Use this when you need to identify your own public IP 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
IPDATA_CO_FIELD_IS_EUTool to return only is_eu for an IP. Use when you need to determine if an IP's country belongs to the EU.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_LANGUAGESTool to return only the languages array for an IP. Use when only language details for an IP are required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_LATITUDETool to return only the latitude for an IP. Use when only the latitude coordinate is needed.
Input parameters
IPv4 or IPv6 address to look up. 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
IPDATA_CO_FIELD_LONGITUDETool to return only longitude for an IP. Use when only the longitude value is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_POSTALTool to return only postal code for an IP. Use when only the postal code (ZIP/postcode) is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_REGIONTool to return only region for an IP. Use when only the region name is required.
Input parameters
IPv4 or IPv6 address to look up; if omitted, uses the calling 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
IPDATA_CO_FIELD_REGION_CODETool to return only region_code for an IP. Use when only the ISO 3166-2 region code is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_THREATRetrieve threat intelligence data for a specific IP address or the calling IP. Returns indicators such as Tor exit node status, proxy detection, datacenter/cloud provider identification, known attacker/abuser flags, and blocklist appearances. Use this tool when you need to assess the security risk or reputation of an IP address.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_FIELD_TIME_ZONETool to return only the time_zone object for an IP. Use when only timezone data is required.
Input parameters
IPv4 or IPv6 address to look up. If omitted, uses the calling 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
IPDATA_CO_IP_DATA_BASIC_ASN_FOR_IPTool to return basic ASN data for a specific IP. Use when you need ASN number, organization, domain, route, and type details.
Input parameters
IPv4 or IPv6 address to look up
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
IPDATA_CO_IPDATA_BULK_LOOKUP_V1Tool to bulk lookup up to 100 IP addresses via ipdata.co. Use when you have multiple IPs and need geolocation and threat data in one call.
Input parameters
List of IPv4 or IPv6 addresses to lookup (1-100).
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
IPDATA_CO_IP_DATA_COMPANY_FOR_IPTool to retrieve company data for a given IP address. Use when you need the organization name, domain, network prefix, and usage type for an IPv4 or IPv6.
Input parameters
Target IPv4 or IPv6 address (e.g. '8.8.8.8' or '2001:4860:4860::8888')
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
IPDATA_CO_IPDATA_EU_LOOKUP_CALLING_IPLookup geolocation, network, and threat data for the calling client's IP address using the EU-residency endpoint. Use this action when you need IP data processed and stored entirely within the European Union (GDPR compliance). The EU endpoint routes requests only through EU datacenters (Frankfurt, Paris, Ireland). This action automatically detects and returns data for the IP address making the API request. No IP address parameter is needed.
Input parameters
Comma-separated list of response fields to include. Available fields: ip, is_eu, city, region, region_code, country_name, country_code, continent_name, continent_code, latitude, longitude, postal, calling_code, flag, emoji_flag, emoji_unicode, asn, carrier, languages, currency, time_zone, threat, company. Example: 'ip,city,country_name,is_eu'. Omit to return all fields.
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
IPDATA_CO_IP_DATA_LOOKUP_IP_V1Tool to lookup comprehensive IP information (geolocation, network, company, and threat data) in one call. Use when you need all IP insights together.
Input parameters
IPv4 or IPv6 address to look up
Comma-separated list of response fields to return, e.g., ip,is_eu,city,region,region_code,country_name,country_code,continent_name,continent_code,latitude,longitude,asn,company,postal,calling_code,flag,emoji_flag,emoji_unicode,carrier,languages,currency,time_zone,threat,count
JSONP callback function name
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 58 agents privately built on Nagent that already use Ipdata.co.
Build on Nagent
Connect Ipdata.co 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 Ipdata.co, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ipdata.co is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ipdata.co is connected, you configure its 28 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ipdata.co 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 Ipdata.co event fires, the agent kicks off automatically.
Every Ipdata.co 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 Ipdata.co ships with 28 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ipdata.co together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ipdata.co-based workflows tailored to your business.