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.
1 endpointsJentic 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.
1 endpointsJentic publishes the only available OpenAPI specification for IP geolocation API, keeping it validated and agent-ready. Abstract's IP geolocation API resolves any IPv4 or IPv6 address to a region, country, and city across 180+ countries, with optional fields for currency, flag, language, timezone, and ISP. The whole API is a single GET endpoint, keyed by an api_key query parameter, returning JSON. It is designed for inline lookups in onboarding, fraud, and personalization flows where a heavier MaxMind or IPinfo install is overkill.
1 endpointsJentic publishes the only available OpenAPI specification for IP geolocation API, keeping it validated and agent-ready. Abstract's IP geolocation API resolves IPv4 and IPv6 addresses to a region, country, and city with optional currency, flag, and language fields, covering 180+ countries. The whole API is a single GET endpoint keyed by an api_key query parameter, returning JSON. It is intended for inline lookups in onboarding, fraud, and personalization flows where a heavier MaxMind or IPinfo install is unnecessary.
1 endpointsStep 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 | shStep 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 instanceJentic 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.