canonical: https://jentic.com/apis/ipgeolocationapi.io/ipgeolocationapi

# ipgeolocationapi.io API

The ipgeolocationapi.io API resolves an IPv4 or IPv6 address to its location, connection, timezone, and currency details, with optional security and company blocks on paid plans. Beyond the IP lookup it converts times between IANA timezones, returns sun and moon events for an IP or coordinates, parses user-agent strings, and looks up ASN details and abuse contacts through RDAP. Responses are drop-in compatible with ipwho.is and can be trimmed with fields and excludes, localised with lang, or returned as JSON, XML, or CSV.

## For AI agents

Look up where an IP address is, which network owns it, and who handles its abuse reports, plus timezone conversion, astronomy times, and user-agent parsing in one key.

## Scope

Does not geocode street addresses, calculate routes, or render maps. Use for IP address geolocation and related network lookups only.

## Capabilities

- Geolocate an IPv4 or IPv6 address, or the caller's own IP, with country, region, city, and connection details
- Trim a lookup response to chosen fields with dot notation such as connection.asn, or drop fields with excludes
- Convert a time between two IANA timezones with the from, to, and time parameters
- Get sunrise, sunset, and moon events for an IP address or for lat and lon coordinates on a date
- Parse a raw user-agent string into its browser, operating system, and device parts
- Look up an ASN's organisation, type, route counts, and prefixes, or the RDAP abuse contact for an IP

## Use cases

### Agent-driven IP triage

An AI agent reviewing suspicious sign-ins needs to know where each IP sits and who to contact about it. Through Jentic the agent searches for 'geolocate an IP address', loads the ipgeolocationapi.io lookup operation, and reads country, city, and connection details, then calls the abuse lookup for the RDAP contact. The key is attached at call time, so the agent works from the lookups without handling the credential.

Example prompt: Call GET /{ip} for 8.8.8.8 with fields set to ip,country,city,connection.asn, then call GET /abuse with ip 8.8.8.8 and report the abuse contact

### Localising content by visitor IP

A web service picks the language, currency, and timezone to show based on the visitor's address. The caller IP lookup returns location, timezone, and currency for the request's own address, and lang localises the country name, so the service can render a regional default before the visitor chooses one.

Example prompt: Call GET / to look up the caller IP and return its country, timezone, and currency fields

### Scheduling across timezones

An assistant booking a call between two cities converts the proposed time from one IANA timezone to another and checks local daylight for an in-person meeting. The timezone conversion read takes from, to, and an optional time, and the astronomy read returns sun and moon events for coordinates and a date.

Example prompt: Call GET `/timezone/convert` with from Europe/Dublin, to America/New_York, and time 2026-11-12T15:00, then call GET /astronomy with lat 40.71 and lon -74.01 for 2026-11-12

### Log enrichment for analytics

A log pipeline adds network and client context to raw request records. The bulk lookup takes up to 100 comma-separated IPs on Business or Max keys, the ASN read returns the organisation and prefixes behind an autonomous system, and the user-agent parser splits the browser and device from each request.

Example prompt: Call GET /bulk with ips set to 1.1.1.1,8.8.8.8,9.9.9.9 and GET /useragent with a Chrome user-agent string, then merge both results into one record per request

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{ip}` | Geolocate an IP address |
| GET | `/` | Look up the caller IP |
| GET | `/bulk` | Look up up to 100 IPs |
| GET | `/abuse` | Get the RDAP abuse contact for an IP |
| GET | `/asn` | Look up an ASN |
| GET | `/timezone/convert` | Convert between IANA timezones |
| GET | `/useragent` | Parse a user-agent string |

## Key resources

- **IP lookup** — Single and caller IP geolocation with fields, excludes, lang, and output options, plus paid security and company blocks
- **Bulk lookup** — Up to 100 IPs in one call on Business or Max keys
- **Timezone and astronomy** — IANA timezone conversion and sun and moon events by IP or coordinates
- **Network data** — ASN details and RDAP abuse contacts
- **User-agent parsing** — Breaks a user-agent string into browser, OS, and device

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 42 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 19 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/ipgeolocationapi.io/ipgeolocationapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring ipgeolocationapi.io by hand means deciding between the X-API-Key header and the key query parameter, and knowing which reads need a paid key. Through Jentic you install once, import ipgeolocationapi.io from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Each ipgeolocationapi.io capability is its own operation, so a rule can bound your agent to the lookups it needs, such as the IP and abuse reads. You choose the operations it may call, so the paid bulk lookup is not included unless you add it.
- **Credential handling:** Your ipgeolocationapi.io key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'geolocate an IP address' or 'convert a time between timezones', and Jentic returns the matching ipgeolocationapi.io operation with its input schema so the agent calls the right endpoint.

## Related APIs

- **ipgeolocation.io** — IP geolocation with timezone and astronomy lookups from a separate provider
- **IPstack** — IP to location lookups with currency and timezone data
- **IP2Proxy** — Proxy and VPN detection to pair with location lookups

## FAQ

### What authentication does the ipgeolocationapi.io API use?

Per its OpenAPI spec, the API declares an API key sent in the X-API-Key header, applied to every operation. The IP lookup and bulk operations also accept the key as a key query parameter. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it.

### What are the rate limits for the ipgeolocationapi.io API?

The spec states a free allowance of 5,000 requests a day with no credit card, and marks bulk lookups and the security and company blocks as paid. It does not list per-plan limits; check https://ipgeolocationapi.io for current plans.

### Can I look up many IP addresses at once with the ipgeolocationapi.io API?

Yes, on paid plans. GET /bulk takes up to 100 comma-separated IPs in the ips parameter and needs a Business or Max key. For single addresses, GET /{ip} accepts fields and excludes to keep responses small.

### Is there an ipgeolocationapi.io MCP server?

You don't need an MCP server to give your agent ipgeolocationapi.io. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the lookup, timezone, and ASN operations on demand without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only GET /{ip} and GET /abuse, for example, and the agent can geolocate addresses and fetch abuse contacts but cannot run paid bulk lookups against your quota. Every call it makes is logged.

### How do I geolocate an IP address through Jentic?

Search Jentic for 'geolocate an IP address', load the GET /{ip} operation, and execute it with the address and an optional fields list such as ip,country,connection.asn. To run it on your own infrastructure, install Jentic One from its GitHub repo.