canonical: https://jentic.com/apis/abstractapi.com/abstractapi-ip-geolocation

# Abstractapi Abstract IP Geolocation API

Jentic publishes the only available OpenAPI specification for Abstract IP Geolocation API, keeping it validated and agent-ready. Abstract's IP Geolocation API resolves IPv4 and IPv6 addresses to a precise location, timezone, currency, and ISP across 4 billion+ addresses and 250,000+ cities, with weekly data refreshes. The service exposes a single GET endpoint and is keyed by an api_key query parameter, returning JSON with optional security and connection-type fields. It is built for inline lookups in onboarding, fraud, personalization, and analytics flows.

## For AI agents

Resolve an IP address to country, region, city, timezone, currency, security flags, and ISP via a single Abstract endpoint authenticated by an api_key query parameter.

## Scope

Does not handle physical address geocoding, routing, or place-of-interest search - use for IP-to-location and IP risk-flag lookups only.

## Capabilities

- Resolve a visitor IP to country, region, and city for personalization
- Detect proxy, VPN, or Tor usage to inform fraud scoring
- Look up the timezone for an IP to schedule notifications correctly
- Identify the ISP and connection type behind an IP
- Return currency and language codes for localized pricing flows

## Use cases

### Fraud check at signup

Call the geolocation endpoint with the signup IP to retrieve country, ISP, and security flags (proxy, Tor, hosting provider) and combine them with other fraud signals before allowing account creation. The response is small and fast enough to inline into the signup path.

Example prompt: Call GET / with ip_address=203.0.113.1 and reject the signup if security.is_vpn or security.is_proxy is true

### Geo-pricing and localization

Resolve the visitor's IP at first page load and use country, currency, and language fields to choose the right storefront variant. Abstract returns ISO country and currency codes plus locale-specific currency_name and currency_symbol so the storefront can render prices correctly.

Example prompt: Call GET / with the visitor's IP and return country_code, currency.currency_code, and timezone.name

### Audit-log enrichment

Attach geolocation data to every audit log entry so security teams can spot anomalous logins. The Abstract response includes country, region, city, latitude, longitude, and ISP - enough to flag impossible-travel events.

Example prompt: For each login event, call GET / with the source IP and append country, city, and isp to the audit record

### AI agent visitor enrichment via Jentic

An agent looking up website visitor or webhook source IPs calls the Abstract endpoint via Jentic to attach geolocation context without storing the api_key. Jentic returns the operation schema on demand so the agent can execute against any IP without prior integration code.

Example prompt: For each incoming webhook IP, call GET / and append country, city, security.is_vpn to the event payload

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | / | Resolve an IP to location, timezone, currency, security, and ISP |

## Key resources

- **IP Geolocation Lookup** — Resolve an IP to country, region, city, timezone, currency, security flags, and ISP via GET /

## Why Jentic

- **Setup:** Wiring the Abstract IP Geolocation API by hand means pointing calls at the ipgeolocation subdomain and appending the api_key query parameter yourself for every resolution. Through Jentic you install once, import the Abstract IP Geolocation API from the API Directory, store the api_key once, and your agent calls it.
- **Permission scoping:** The lookup takes the api_key and target IP as query parameters with no resource id in the URL, so limit the agent to the operations it needs, namely IP-to-location and risk-flag resolution. You choose the operations it may call, so nothing beyond that lookup runs unless you add it.
- **Credential handling:** Your Abstract api_key is stored once, encrypted, by your own Jentic One instance and injected as the api_key query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'detect country from ip' or 'check vpn from ip', and Jentic returns the matching Abstract operation with its input schema so the agent calls the endpoint without browsing the reference docs.

## Related APIs

- **ipstack** — IP-to-location with security and currency modules
- **MaxMind** — GeoIP2 web service and downloadable databases
- **ipgeolocation.io** — IP geolocation with timezone, astronomy, and abuse contact endpoints

## FAQ

### Why is there no official OpenAPI spec for Abstract IP Geolocation API?

Abstract API does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Abstract IP Geolocation API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Abstract IP Geolocation API use?

Authentication is an api_key query parameter on the single GET / endpoint. There is no OAuth or header-based auth. Through Jentic the api_key is held in the vault and injected at execution, so the agent never sees the raw key.

### Can I detect VPN or proxy usage with this API?

Yes. The response includes a security object with is_vpn, is_proxy, is_tor, and is_hosting flags. These can be used directly as fraud signals or stacked with risk scores.

### What are the rate limits for the Abstract IP Geolocation API?

The free tier allows 20,000 requests per month at 1 request per second; paid plans raise both quota and concurrency. Limits are not encoded in the spec - check your Abstract dashboard for the live values.

### How do I check if an IP is from a VPN through Jentic?

Search Jentic for 'detect vpn from ip', load the GET / operation on ipgeolocation.abstractapi.com/v1, then execute with the IP. Install with pip install jentic and use await client.search, load, execute.

### Is the Abstract IP Geolocation API free?

Yes, with a 20,000 requests/month free tier. Paid plans add SLA, HTTPS-only options, and higher concurrency. The response schema is identical across tiers.

### Can I limit what my agent is allowed to do with the Abstract IP Geolocation API?

Yes. Because Jentic One is self-hosted, you decide which operations and credentials your agent may use, and this API exposes only a single GET lookup that resolves an IP to location and risk flags. You can restrict the agent to that one IP-to-location and risk-flag resolution, and since the request takes only the api_key and target IP as query parameters with no resource id in the URL, there is nothing else it can reach. Nothing beyond that lookup runs unless you explicitly grant it.