Abstractapi IP geolocation API

Name: IP geolocation API
Brand: IP geolocation API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationGeocodingapiKey1 EndpointsREST

For Agents

Resolve any IPv4 or IPv6 address to country, region, city, timezone, currency, and language using a single Abstract endpoint authenticated by an api_key query parameter.

Install Jentic One Beta

Connect the IP geolocation API to your agent

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

Resolve a visitor IP to country, region, and city for personalization

Detect the user's currency and language from their IP for localized pricing

Look up the timezone of an IP for scheduling and timestamp display

GET STARTED

Start building with IP geolocation API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use IP geolocation API for, with concrete tasks.

★ Localize pricing by visitor IP

Call the geolocation endpoint on every page load to derive the visitor's country and currency, then show prices in the local currency. Returns within a few hundred milliseconds and covers 180+ countries, so it works as a drop-in replacement for heavier on-prem GeoIP databases.

Call GET /v1/ with ip_address=8.8.8.8 and return country_code and currency.currency_code

Fraud signal for signups

Compare the country derived from the signup IP with the user-supplied billing country, and flag mismatches for review. The geolocation response includes country_code, region, and ISP fields useful for stacking with other fraud signals.

Call GET /v1/ with the signup IP and compare country_code with user-supplied country, returning a mismatch boolean

Timezone-aware scheduling

When a user creates a meeting or schedules a notification, call the geolocation endpoint to derive their timezone from their IP and pre-fill the timezone selector. Avoids forcing users to pick from a dropdown.

Call GET /v1/ with the request IP and return timezone.name and timezone.gmt_offset

AI agent visitor profiling

An agent enriching website visitor records calls the geolocation endpoint to attach country, city, and ISP to each session, all via Jentic so the api_key never enters the agent context. The response shape is small and stable, so the enriched record can be passed straight to a CRM or analytics pipeline.

For each visitor session, call /v1/ with the session IP and append country, city, and connection.connection_type to the visitor record

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/v1/

Resolve an IP address to country, region, city, timezone, and ISP

GET

/v1/

Resolve an IP address to country, region, city, timezone, 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. When an agent executes the geolocation lookup, Jentic injects the key as the api_key query parameter at runtime, so the secret never enters the agent's prompt or memory.

Intent-based discovery

Agents search Jentic by intent (e.g. 'find country from ip address') and Jentic returns the matching Abstract operation with its input schema, so the agent calls the endpoint without reading docs.

Time to first call

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

FAQs

Specific to using IP geolocation API through Jentic.

Why is there no official OpenAPI spec for 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 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 IP geolocation API use?

The endpoint requires an api_key query parameter — there is no header-based auth. Through Jentic the api_key is held encrypted in the vault and injected at execution time, so the agent never sees the raw secret.

Can I look up an IPv6 address with this API?

Yes. GET /v1/ accepts both IPv4 and IPv6 in the ip_address query parameter and returns the same response shape. If ip_address is omitted the endpoint defaults to the requester's own IP.

What are the rate limits for the IP geolocation API?

Limits are tied to your Abstract plan, not to the spec. The free tier is 20,000 requests/month with 1 request/second; paid tiers raise both quota and concurrency. Check your Abstract dashboard for current numbers.

How do I look up a country from an IP through Jentic?

Search Jentic for 'look up country from ip address', load the operation that maps to GET /v1/ on ipgeolocation.abstractapi.com, then execute with ip_address. Install with pip install jentic and use the async pattern.

Is the Abstract IP geolocation API free?

Yes, the free tier covers up to 20,000 lookups per month at 1 request per second. Paid tiers add HTTPS-only options, higher concurrency, and SLA, but the response schema is the same across tiers.