Abstractapi Abstract IP Geolocation API

Name: Abstract IP Geolocation API
Brand: Abstract IP Geolocation API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationGeocodingapiKey1 EndpointsREST

For 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.

Install Jentic One Beta

Connect the Abstract IP Geolocation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Abstract 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 Abstract IP Geolocation API.

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

GET STARTED

Start building with Abstract IP Geolocation API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ 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.

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.

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.

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.

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

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for abstract ip geolocation api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/

Resolve an IP to location, timezone, currency, security flags, and ISP

GET

/v1/

Resolve an IP to location, timezone, currency, security flags, and ISP

Why Jentic?

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

Credential isolation

The Abstract api_key is stored encrypted in the Jentic vault. Jentic injects it as the api_key query parameter at runtime so the agent never sees the raw secret.

Intent-based discovery

Agents search Jentic by intent (e.g. 'detect country from ip', 'check vpn from ip') and Jentic returns the matching Abstract operation with its input schema.

Time to first call

Direct integration: 2-4 hours including auth, retries, and security-flag handling. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using Abstract IP Geolocation API through Jentic.

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 at https://app.jentic.com/sign-up.

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.