canonical: https://jentic.com/apis/abstractapi.com/abstractapi-main

# Abstractapi Abstract IP Geolocation API

Jentic publishes the only available OpenAPI specification for Abstract IP Geolocation API, keeping it validated and agent-ready. Abstract IP Geolocation provides lookup of geolocation data for any IPv4 or IPv6 address, including city, region, country, timezone, currency, language, and security signals. The whole API is a single GET /v1/ endpoint keyed by an api_key query parameter, returning JSON. It is a drop-in replacement for self-hosted GeoIP databases when you only need a few hundred lookups per second.

## For AI agents

Resolve any IP address to country, region, city, timezone, currency, security flags, and ISP using 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, Tor, or hosting-provider origins for fraud scoring
- Look up the timezone of an IP for scheduling and timestamp display
- 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) and combine them with other fraud signals before allowing account creation. Response is small and fast enough to inline into the signup path.

Example prompt: Call GET /v1/ 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 labels so the storefront can render prices correctly.

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

### Audit log enrichment

Attach geolocation to login and security audit log entries so reviewers can spot anomalous geographies. The Abstract response includes country, region, city, latitude, longitude, and ISP - enough to flag impossible-travel events.

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

### AI agent visitor enrichment via Jentic

An agent enriching webhook source IPs or visitor records calls the Abstract endpoint via Jentic to attach country, city, and security flags 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 /v1/ and append country, city, security.is_vpn to the event payload

## Key endpoints

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

## Key resources

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

## 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 on each lookup. 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?

An api_key query parameter on GET /v1/. There is no OAuth or header-based auth. Through Jentic the api_key is held encrypted in the vault and injected at execution, so the agent never sees the raw secret.

### 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?

Free tier: 20,000 requests/month at 1 request/second. Paid tiers raise both. Limits are not encoded in the spec - check your Abstract dashboard for 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 /v1/ operation on ipgeolocation.abstractapi.com, 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 lookups/month free tier. Paid plans add SLA, HTTPS-only options, and higher concurrency. Response schema is identical across tiers.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API exposes a single GET /v1/ lookup that takes the api_key and target IP as query parameters with no resource id in the URL, so you can restrict the agent to just that IP-to-location and risk-flag resolution. Nothing beyond that lookup runs unless you explicitly add it, and your Abstract api_key is injected at execution time so the agent never handles the raw secret.