Ipdata.co

Enriches every incoming request with location, network, and security data to automate fraud detection and regional routing.

Try Ipdata.co in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Ipdata.co integration

    • Describe the outcome and Ceven picks the right Ipdata.co calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Ipdata.co data, across all 28 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Ipdata.co access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Ipdata.co, when, and on whose behalf.
    • The agent pauses and asks when Ipdata.co is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Ipdata.co.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Ipdata.co action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Ipdata.co, and when to use it.

Lookup IP
Pull comprehensive geolocation, network, company, and threat data for a specific IP in one call.
Get Threat Intel
Use this when you need to determine if an IP is a Tor node, VPN, proxy, datacenter, or listed on blocklists.
Bulk Lookup IPs
Pull geolocation and threat data for up to 100 IP addresses in a single request for batch processing.
Get Company Data
Pull the organization name, domain, network prefix, and usage type for an IPv4 or IPv6 address.
Advanced ASN Lookup
Pull detailed ASN information including prefixes, peers, and registry details after confirming an ASN number.
Get Carrier Data
Pull mobile carrier name, MCC, and MNC for a specific IP address to identify mobile users.
EU Specific Lookup
Use this when you need IP lookup processed and stored within the EU to meet data residency requirements.
Get Time Zone
Pull timezone name, abbreviation, offset, and current local time for a specific IP.
Get Currency
Pull the currency object based on the geolocation of a specific IP address.
Get City
Pull only the city name for a specific IP address to minimize data payload.
Get Country Code
Pull only the 2 letter ISO country code for a specific IP.
Check EU Status
Use this to determine if an IP country belongs to the European Union.
Get Carrier Data for an IP
Tool to return mobile carrier data for a specific IP. Use when you need carrier name, MCC, and MNC for an IP address.
EU specific IP lookup
Tool to lookup a specific IP address via the EU only data residency endpoint. Use when you need IP lookup processed and stored within the EU.
IPData: Calling Code
Tool to fetch the international calling_code for an IP's country. Use when you need only the calling code field from ipdata_co.
IPDATA Field Carrier
Tool to return only the carrier object for the calling IP. Use when you need mobile carrier details of a specific IP.
Get City from IP
Tool to return only city for an IP. Use when only the city name is required.
IPData: Continent Code
Tool to return only continent_code for an IP. Use when only the continent code is required.
Get Continent Name from IP
Tool to return only continent name for an IP. Use when only the continent name is required.
IPDATA Field Count
Tool 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.
IPData: Country Code
Tool to return only country_code for an IP. Use when only the 2-letter country code is required.
Get Country Name from IP
Tool to return only country name for an IP. Use when only the country name is required.
IPDATA Field Currency
Tool to return only currency object for an IP. Use when currency details are needed.
Get Emoji Flag from IP
Tool to return only emoji flag for an IP. Use when only the country flag emoji is required.
Get Emoji Unicode from IP
Tool to return only emoji_unicode for an IP. Use when only the Unicode country flag emoji is required.
IPData: IP
Tool to return only the caller’s IP string. Use when you need just the origin IP of your request.
IPData: Is EU
Tool to return only is_eu for an IP. Use when you need to determine if an IP's country belongs to the EU.
IPData: Languages
Tool to return only the languages array for an IP. Use when only language details for an IP are required.
IPData: Latitude
Tool to return only the latitude for an IP. Use when only the latitude coordinate is needed.
Get Longitude from IP
Tool to return only longitude for an IP. Use when only the longitude value is required.

30 actions · scroll to see them all

Frequently asked questions

Ceven stores your Ipdata API key in an encrypted vault that is isolated from the model training set. When a workflow triggers an Ipdata action, the agent retrieves the key at runtime to sign the HTTP request and then immediately purges it from the active memory. You can rotate your key in the Ipdata dashboard and update it in the Ceven connection settings without needing to rewrite any of your existing workflows. We never share these keys with third parties and they are only used to facilitate the specific API calls requested by your automated agents.
Ceven monitors the HTTP response codes from Ipdata in real time. If the API returns a 429 Too Many Requests error, the agent will enter a retry loop with exponential backoff. If the limit is fully exhausted for the billing cycle, the workflow will pause and send a notification to the admin. Because Ipdata uses a credit based system, you can set up a Ceven alert that triggers when your request count reaches 80 percent of your monthly quota so you can upgrade your plan before any critical security workflows are interrupted.
Yes. Ceven provides specific actions that route requests through the EU only data residency endpoint. This ensures that the IP address and the resulting geolocation data are processed and stored within the European Union. To use this, you must select the EU specific lookup action rather than the standard lookup. This is critical for companies that have strict data processing agreements requiring that PII such as IP addresses never leave the EU region during the enrichment process for compliance audits.
The threat intelligence provided by Ipdata is updated frequently to track the volatile nature of proxies and VPNs. Ceven pulls this data in real time, meaning you get the most current status of whether an IP is a known Tor node or a public proxy. While no database is 100 percent perfect, combining the threat object with other signals like ASN type and company data allows the Ceven agent to create a high confidence risk score for each request.
Ceven can handle bulk lookups using the Ipdata Bulk Lookup V1 endpoint which supports up to 100 IPs per call. If you have a log file with thousands of entries, the Ceven agent will automatically chunk the data into groups of 100 and execute sequential calls. It then aggregates the results into a single structured format like a CSV or a database table. This prevents the workflow from timing out and ensures that you stay within the API limits while processing large volumes of security telemetry.
Yes, Ipdata supports both IPv4 and IPv6 addresses. When the Ceven agent passes an IP to the API, Ipdata automatically detects the version and returns the corresponding geolocation and network data. This is particularly useful for modern mobile networks where IPv6 is the primary protocol. The agent can then normalize this data so that your downstream security tools receive a consistent format regardless of whether the original connection was IPv4 or IPv6.
The free tier of Ipdata has a strict daily limit on the number of requests you can make. A key quirk of the free tier is that certain advanced fields, such as detailed threat intelligence or specific ASN data, may be restricted or limited compared to paid plans. If you are using a free key, you might notice that the threat object returns empty or limited results. Ceven will report these as null values in your workflow, so we recommend a paid plan for production security workflows that rely on threat detection.
No. Ipdata provides geolocation at the city and postal code level, but it cannot provide a specific street address or house number. This is a limitation of how IP geolocation works across the entire industry. The data is based on registration records and network routing, which gives a general area but not a precise physical location. Ceven uses this for regional routing and fraud analysis, but it should not be used for precise physical tracking of individuals.

Alternatives to Ipdata.co

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Ipdata.co and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free