ip-api Geolocation API
★ Only Publicly Available OpenAPI DocumentData EnrichmentAddress Validationnone3 EndpointsREST
For Agents
Resolve any IP address or hostname to country, city, ISP, ASN, and timezone so an agent can enrich logs, route users, or apply geo-based rules.
Use for: I need to geolocate an IP address, Find the country and city for 8.8.8.8, Look up the ISP behind a list of IP addresses, Get the timezone for a given IP
Not supported: Does not handle proxy or VPN detection, threat intelligence, or domain WHOIS — use for IP and hostname geolocation only.
Jentic publishes the only available OpenAPI specification for ip-api Geolocation API, keeping it validated and agent-ready. ip-api is a free IP geolocation service that returns country, region, city, latitude and longitude, ISP, organisation, AS number, and timezone for any IPv4 or IPv6 address or hostname. The free tier is HTTP-only and limited to non-commercial use; the pro tier at https://pro.ip-api.com adds HTTPS and higher rate limits. The 3-endpoint surface covers single-IP lookups, requester-IP lookups, and a batch endpoint that resolves up to 100 IPs in one call.
Install Jentic One Beta
Connect the ip-api Geolocation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ip-api 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.
1
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 | sh2
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 instanceJentic 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 ip-api Geolocation API.
Resolve any IPv4 or IPv6 address to country, region, city, latitude, and longitude
Look up the ISP, organisation, and AS number behind an IP address
Geolocate the IP that issued the current request without supplying it explicitly
Batch up to 100 IP addresses into a single POST for log-enrichment workloads
Resolve a hostname through the same endpoint as an IP for hybrid lookups
Return the local timezone for an IP for time-of-day routing decisions
Use Cases
Patterns agents use ip-api Geolocation API for, with concrete tasks.
★ Web Log Enrichment
Operations and security teams can enrich raw web access logs with country, city, and ISP data by feeding IPs through the batch endpoint, which accepts up to 100 IPs per POST. The output adds geographic context to dashboards and lets analysts spot unusual traffic patterns without standing up a local MaxMind database.
Send a batch of 50 IP addresses to /batch and return the country and ISP for each one as a CSV.
Geo-Aware Routing
Web applications can call /json/ on a request to obtain the visitor's country and city without supplying the IP explicitly, then route to the closest CDN region or apply locale-specific content rules. The lookup is cheap enough to do on the request path during cold starts.
Call /json/ with no IP from the server-side handler and route the response to the EU bucket if country is in the EU country list.
Fraud and Abuse Triage
Trust and safety teams can geolocate IPs surfaced in abuse reports to spot mismatches with the account country, then escalate or block. ip-api returns ISP, ASN, and country in a single call, which is the minimum needed to triage a low-effort fraud signal.
Geolocate the IP from a flagged login event and report whether the country differs from the account billing country.
Agent-Driven Log Triage
An AI agent connected via Jentic can enrich a list of suspect IPs with country, ISP, and ASN, summarise the result, and decide whether to escalate or close. The agent searches Jentic by intent rather than wiring the three ip-api endpoints by hand, and Jentic injects the right base URL when an account upgrades to pro.ip-api.com.
Take a list of 25 IPs from a security alert, batch-resolve them via /batch, and return a summary grouped by country and ASN.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for ip-api geolocation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/json/{query}
Geolocate an IP address or hostname
GET
/json/
Geolocate the requesting IP
POST
/batch
Batch geolocate up to 100 IPs
GET
/json/{query}
Geolocate an IP address or hostname
GET
/json/
Geolocate the requesting IP
POST
/batch
Batch geolocate up to 100 IPs
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The free ip-api endpoint is unauthenticated, so Jentic just routes the call. For pro accounts the 'key' query parameter is held in the Jentic vault and injected at execution time so the raw key never reaches the agent context.
Intent-based discovery
Agents search Jentic for 'geolocate an IP' or 'batch IP lookup' and Jentic returns the matching ip-api operation with its input schema, so the agent does not have to keep the three endpoints in context.
Time to first call
Direct ip-api integration: under an hour for the free path. Through Jentic: a few minutes to search, load, execute and start enriching IPs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ip-api Geolocation API through Jentic.
Why is there no official OpenAPI spec for ip-api Geolocation API?
ip-api does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ip-api Geolocation API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the ip-api Geolocation API use?
The free tier at http://ip-api.com requires no authentication. The pro tier at https://pro.ip-api.com requires an API key passed as the 'key' query parameter; through Jentic that key is held in the encrypted vault and appended at execution time.
Can I batch lookups instead of calling once per IP?
Yes. POST a JSON array of up to 100 IP addresses or hostnames to /batch and the response returns one entry per query in the same order. This is the recommended pattern for log enrichment workloads.
What are the rate limits for the ip-api Geolocation API?
The free endpoint allows 45 requests per minute per source IP and the response includes X-Rl and X-Ttl headers showing remaining quota and reset time. The pro tier removes that limit and the documentation lists the per-plan throughput.
How do I geolocate an IP through Jentic?
Search Jentic for 'geolocate an IP address', load the schema for GET /json/{query}, and execute with the IP. Run pip install jentic, then await client.search, await client.load, await client.execute.
Does ip-api support IPv6 and hostnames?
Yes. The /json/{query} endpoint accepts IPv4 addresses, IPv6 addresses, and hostnames; the response shape is the same for all three so an agent does not need to branch on input type.
GET STARTED