canonical: https://jentic.com/apis/apiip.net/apiip

# Apiip - IP Geolocation API

The Apiip API resolves IP addresses to geographic and network details over a REST interface. It returns the country, region, city, coordinates, currency, timezone, and connection data for the caller's own IP or any address supplied, and it can look up several addresses in a single request. Calls authenticate with an API key passed as a query parameter.

## For AI agents

Lets an AI agent resolve IP addresses to location, currency, and timezone data, including batch lookups of several addresses at once.

## Scope

Resolves IP addresses to location and network data only; it does not geocode street addresses or provide mapping tiles, so pair it with a geocoding service for address lookups.

## Capabilities

- Resolve the caller's own IP address to location data
- Look up geolocation details for a specified IP address
- Resolve several IP addresses in a single batch request
- Return country, region, city, and coordinate data
- Return currency, timezone, and connection details for an IP

## Use cases

### Localize content by visitor IP

Websites and apps tailor content to where a visitor is. The Apiip API resolves the caller's IP to its country, region, city, and currency, so an integration can pick the right language, currency, or regional offer without asking the user.

Example prompt: Resolve the current visitor's IP address and return the country and preferred currency.

### Enrich records with location data

Analytics and security workflows enrich logged IP addresses with geographic context. The API looks up any supplied address and returns region, city, coordinates, timezone, and connection details, letting an integration annotate records for reporting or risk scoring.

Example prompt: Given an IP address, return its city, coordinates, and timezone.

### Batch-resolve many addresses

Backfilling location data for a set of stored IPs is slow one call at a time. The API accepts several addresses in one request and returns their geolocation details together, so an integration can process a list efficiently.

Example prompt: Given a list of IP addresses, resolve them in one request and return each location.

### Let an agent geolocate IP addresses

An AI agent that handles support or security tasks can attach location context to an IP on demand. Through Jentic the agent discovers the lookup by intent and runs it under the integration's own API key, returning country, city, and timezone for the address in question.

Example prompt: Given an IP from a support ticket, return the country, city, and timezone to the user.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/check` | Resolve the caller's own IP address |
| GET | `/api/check/{ip}` | Resolve a specified IP address |
| GET | `/api/check/{ips}` | Resolve several IP addresses in one request |

## Key resources

- **Own IP lookup** — Resolve the location of the caller's own IP address
- **IP lookup** — Resolve geolocation details for a specified IP address
- **Batch lookup** — Resolve several IP addresses in a single request

## Why Jentic

- **Setup:** Wiring up IP geolocation yourself means integrating the endpoint, tracking the API key, and handling batch requests. With Jentic you install once, import Apiip from the Directory, and store the access key a single time.
- **Permission scoping:** Running Jentic in your own instance, you decide which Apiip operations the agent may call, so you can allow single lookups while withholding batch lookups. Access is granted per operation.
- **Credential handling:** Your Apiip access key is held encrypted by your own Jentic One instance and injected only when a lookup runs, so it never appears in the agent's prompt, logs, or context.
- **Discovery method:** Agents find Apiip through Jentic's intent search: a request like resolve this IP to a country resolves to the right operation with inputs and auth prepared.

## Related APIs

- **AbstractAPI IP Geolocation** — Resolves IP addresses to location and network data over REST.
- **ipgeolocation.io** — Provides IP geolocation with timezone and astronomy data.
- **LocationIQ** — Geocodes street addresses to coordinates and reverse geocodes.

## FAQ

### Is there an MCP server for the Apiip API?

You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call Apiip lookups directly by intent, so you connect the API without maintaining separate MCP tooling.

### Can I limit which Apiip operations my agent is allowed to call?

Yes. Because you run Jentic yourself, you decide which Apiip operations your agent can call, so you can allow single lookups while withholding batch lookups if you wish. Scoping is applied per operation.

### What authentication does the Apiip API use?

Apiip authenticates with an API key sent as the `accessKey` query parameter. Jentic injects the key from your stored credential when a lookup runs, so it never appears in your agent's prompt.

### Can Apiip resolve more than one IP address at a time?

Yes. Alongside single-address lookups, the API accepts several IP addresses in one request and returns each address's location data together.

### What data does an Apiip lookup return?

A lookup returns country, region, city, and coordinates along with currency, timezone, and connection details for the address, so you can localize content or enrich records.

### How does an agent find the Apiip lookup in Jentic?

The agent searches Jentic by intent, such as resolving an IP to its country, and Jentic returns the matching Apiip operation ready to run under your credentials.