IP2Location.io IP Geolocation API

Name: IP2Location.io IP Geolocation API
Brand: IP2Location.io IP Geolocation API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentAddress ValidationapiKey1 EndpointsREST

For Agents

Install Jentic One Beta

Connect the IP2Location.io IP Geolocation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IP2Location.io IP Geolocation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with IP2Location.io IP Geolocation API.

Resolve any IPv4 or IPv6 address to country, region, city, and ZIP code

Return ISP, domain, ASN, and connection type for an IP address

Surface proxy, VPN, and TOR flags alongside the geolocation response

GET STARTED

Start building with IP2Location.io IP Geolocation API

Explore with Jentic

View OpenAPI Document

IP2Location.io IP Geolocation API is a RESTful, JSON-first geolocation service that resolves an IPv4 or IPv6 address to country, region, district, city, latitude and longitude, ZIP code, time zone, ASN, ISP, domain name, network speed, weather station, mobile carrier, elevation, and usage type. The single-endpoint surface accepts the API key as a query parameter and returns the requested fields in a flat JSON object. It is a modern alternative to the legacy api.ip2location.com surface for teams that want a simple HTTPS lookup with proxy and VPN flags included.

Use Cases

Patterns agents use IP2Location.io IP Geolocation API for, with concrete tasks.

★ Visitor Geolocation for Personalisation

Web applications can call the endpoint with the visitor IP and read country, city, and time zone to personalise content, route to the closest region, or pre-fill a currency selector. The single-endpoint surface keeps the integration small enough to do on the request path during cold starts.

Look up a visitor IP and return the country code, city, and currency for content personalisation.

Log Enrichment with Proxy Flags

Operations and security teams can enrich access logs with country, ISP, ASN, and proxy or VPN flags in one call, then aggregate the result into per-region and per-network dashboards. Bundling proxy detection into the geolocation response avoids a second API for trust signals.

For each unique IP in a log file, call IP2Location.io and write country, ISP, asn, and is_proxy back to the row.

Trust and Safety Triage

Risk teams can flag accounts whose recent logins resolve to commercial VPNs, hosting providers, or known proxy ranges. The response includes is_proxy, proxy_type, and usage_type so the triage decision is a single API call.

Look up an IP and raise a risk flag if is_proxy is true or usage_type is 'DCH'.

Agent-Driven IP Enrichment

An AI agent connected via Jentic can enrich a list of suspect IPs with location, ISP, and proxy flags by issuing one search query through Jentic. The agent does not need to remember the query parameters; Jentic surfaces the input schema with the optional fields documented.

For each IP in a list of 25, call IP2Location.io via Jentic and return a JSON summary keyed by IP with country, isp, and is_proxy.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your IP2Location.io API key is stored once, encrypted, by your own Jentic One instance and injected as the 'key' query parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'geolocate an IP' or 'flag a VPN', and Jentic returns the IP2Location.io lookup operation with its input schema, including the optional fields parameter for trimming responses, so the agent calls the right endpoint without reading the docs.

Time to first call

FAQs

Specific to using IP2Location.io IP Geolocation API through Jentic.

What authentication does the IP2Location.io API use?

The endpoint accepts an API key as the 'key' query parameter. Through Jentic the key is held in the encrypted vault and appended at execution time so the raw key never enters the agent context.

Can the IP2Location.io API tell me whether an IP is a VPN?

Yes. The response includes is_proxy and proxy_type fields on plans that enable proxy detection, and usage_type identifies hosting and data-center IPs that often carry commercial VPN traffic.

Does the IP2Location.io API support IPv6?

Yes. The same endpoint accepts IPv4 and IPv6 addresses and returns the same JSON shape for both, so an agent can pass either family without branching.

What are the rate limits for the IP2Location.io API?

Throughput is governed by the credit balance on the API key rather than a per-minute rate limit; each lookup consumes one credit and richer plans surface more fields. Remaining credits are visible in the IP2Location.io account dashboard.

How do I geolocate an IP through Jentic?

Search Jentic for 'geolocate an IP with IP2Location.io', load the schema for GET /, and execute with the ip parameter. Run pip install jentic, then await client.search, await client.load, await client.execute.

What is the difference between IP2Location.io and api.ip2location.com?

IP2Location.io is the modern JSON-first hosted surface with proxy detection bundled in; api.ip2location.com is the legacy surface that uses a 'package' parameter to select fields. Pick the .io surface for new builds.

Can I limit what my agent is allowed to do with the IP2Location.io API?

Yes. IP2Location.io exposes a single read-only lookup where the IP travels as a query parameter, and because your Jentic One instance is self-hosted, your own rules decide which operations and credentials the agent may use. You can scope the agent to just the lookup operations it needs, such as geolocating an IP or reading its proxy and VPN flag, and it cannot act beyond the operations you allow. The stored API key is injected only when the agent calls an operation you have permitted, so it stays a read-only lookup client.