canonical: https://jentic.com/apis/ipdata.co/main

# ipdata.co IP Enrichment API

ipdata is an IP enrichment API that returns geolocation, threat intelligence, mobile carrier, timezone, currency, and ASN data for any IP address. A lookup resolves a single address or a chosen field, and a bulk endpoint enriches many addresses at once. The service offers separate United States and European hosts so callers can keep requests in a chosen region.

## For AI agents

Lets an AI agent enrich IP addresses through ipdata with geolocation, threat, carrier, and ASN data for single, field-level, or bulk lookups.

## Scope

Does not handle IP blocking, DNS resolution, or user tracking. Use it for IP geolocation and enrichment lookups only.

## Capabilities

- Geolocate an IP address with country, region, and city
- Return threat intelligence flags for an IP
- Resolve mobile carrier, timezone, and currency for an IP
- Look up ASN and network ownership for an IP
- Enrich many IP addresses in a single bulk request
- Request a single field for an IP to trim the response

## Use cases

### IP risk and geolocation enrichment

A fraud or access flow needs both where an IP is and whether it is risky. ipdata returns geolocation alongside threat intelligence flags, carrier, and ASN in one lookup, so an application can score a request from a single call. Field-level lookups trim the response when only one attribute is needed.

Example prompt: Look up an IP and return its country, ASN, and threat flags

### Bulk address enrichment with residency

A pipeline needs enrichment for many IPs while keeping data in a chosen region. ipdata accepts a bulk request and offers United States and European hosts, letting a team enrich logs at volume through the endpoint that fits their residency requirements. Each result carries the full enrichment record.

Example prompt: Send a batch of IP addresses to the European host and return the enrichment record for each

### AI agent request scoring

An AI agent evaluating an incoming request can enrich the source IP before it acts. The agent resolves geolocation, carrier, and threat flags, and uses them to decide whether to proceed, with the lookup gated behind the operation the operator has allowed. All calls are read-only.

Example prompt: Given a source IP, resolve its threat flags and country and return a proceed or block signal

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | Look up the calling device's IP |
| GET | `/{ip_address}` | Look up a specific IP address |
| GET | `/{ip_address}/{field}` | Look up a single field for an IP |
| POST | `/bulk` | Bulk IP address lookup |

## Key resources

- **Standard lookup** — Resolve a single IP address to its full enrichment record
- **Field lookup** — Return a single field for an IP address
- **Bulk lookup** — Enrich many IP addresses in one request
- **Requester lookup** — Return enrichment for the calling device's own IP

## Why Jentic

- **Setup:** Wiring ipdata by hand means provisioning an api-key, choosing between the United States and European hosts for data residency, and appending the key as a query parameter on every call. Install Jentic One once, import the API from the Jentic API Directory, and store the credential once for your agent to reuse.
- **Permission scoping:** Scope your agent to the lookup operations it needs, since every ipdata call is a read against the enrichment service. You decide which operations are callable, and you can point an agent at a single regional host.
- **Credential handling:** Your ipdata key is stored once, encrypted, by your own Jentic One instance and injected only at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents find ipdata through Jentic's intent search: a query such as 'enrich an IP address' matches the lookup operations, which the agent then calls with your stored credential.

## Related APIs

- **IP-API** — IP geolocation lookups with a free tier
- **IP2Location.io** — IP geolocation with detailed location and network fields
- **IP2Proxy** — Detect proxies, VPNs, and anonymizers behind an IP
- **Abstract API** — A suite of enrichment APIs including IP geolocation and validation

## FAQ

### What can an AI agent do with the ipdata API?

An agent can enrich an IP address with geolocation, threat intelligence, mobile carrier, timezone, currency, and ASN data, request a single field, or enrich many addresses in a bulk request. It is a read-only IP enrichment service.

### How does the ipdata API authenticate?

ipdata authenticates with an api-key passed as a query parameter on each request. Jentic injects the key at execution time so it stays out of the agent's context.

### Can I limit what my agent is allowed to do with the ipdata API?

Yes. Your Jentic One instance decides which operations an agent may call, so you can permit only the lookups a workflow needs. Because every ipdata call is read-only, an agent can never modify data through it.

### Does ipdata support regional data residency?

Yes. ipdata offers separate United States and European hosts, so you can send lookups to the regional endpoint that fits your data residency needs. Both hosts expose the same enrichment fields.

### How do I connect the ipdata API to my AI agent with Jentic?

Install Jentic One with its setup script, import the ipdata API from the Jentic API Directory, and store your key once. Your agent can then call the lookup operations you allow.