Apiip - IP Geolocation API
Browse all Apiip APIs✓ Official Vendor SpecMaps GeolocationGeocodingapiKey3 EndpointsREST
For Agents
Resolve any IPv4 or IPv6 address to city, country, timezone, and currency through three lookup endpoints under /api/check.
Use for: Look up the geolocation of IP address 8.8.8.8, Resolve a list of visitor IPs to their countries in one call, Get the timezone for the IP that just hit our server, Find the currency a user's IP suggests they should be billed in
Not supported: Does not handle DNS resolution, ASN ownership lookups, or VPN/proxy detection — use for IP-to-location enrichment only.
Apiip is an IP geolocation service that resolves a single IP, the requester's IP, or a comma-separated batch of up to many IPs to detailed location records. Each lookup returns city, region, country, latitude and longitude, ISO codes, timezone, currency, and connection metadata in a JSON response. The API exposes three GET endpoints rooted at /api/check and authenticates via an accessKey query parameter. It is well suited for fraud signals, content localization, and routing visitors to the nearest data centre.
Install Jentic One Beta
Connect the Apiip - IP Geolocation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Apiip - 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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with Apiip - IP Geolocation API.
Resolve the caller's own IP to a full geolocation record without supplying an address
Look up a single IPv4 or IPv6 address with one GET to /api/check/{ip}
Batch-resolve a comma-separated list of IPs in one request via /api/check/{ips}
Retrieve ISO country, region, and city codes alongside human-readable names for downstream filtering
Read timezone, currency, and connection details to drive localized pricing and content
Restrict response fields with the fields query parameter to minimise payload size and cost
Use Cases
Patterns agents use Apiip - IP Geolocation API for, with concrete tasks.
★ Login fraud signals
When a user logs in, resolve their source IP to country and connection type and compare against the account's usual location pattern. A sudden jump from one country to another or a switch to a hosting/VPN connection is a useful additional signal alongside device fingerprinting. Apiip's /api/check/{ip} endpoint returns these fields in a single low-latency call.
GET /api/check/198.51.100.42?accessKey=...&fields=countryCode,city,connection to fetch the country and connection type for the login event.
Localized pricing and content
Show prices in the visitor's local currency and surface region-specific banners by resolving their IP at first request. Apiip returns currency code, ISO country, and timezone in one response so the frontend can render the right currency symbol and the backend can apply regional tax rules. The whole call typically completes well under 100 milliseconds, fast enough for first-request use.
GET /api/check?accessKey=...&fields=currency,countryCode,timezone using the visitor's IP from the request to drive localized rendering.
Bulk enrichment of access logs
Enrich web analytics or security logs by batch-resolving IPs through /api/check/{ips}, passing a comma-separated list to amortise HTTP overhead. The response is an array of records aligned to the input order, suitable for a nightly enrichment job that joins the data into a warehouse table. This avoids a per-row API call from the analytics database and stays within rate limits.
GET /api/check/8.8.8.8,1.1.1.1,9.9.9.9?accessKey=...&fields=ip,countryCode,city to enrich a batch of log entries.
Agent-driven location reasoning
An agent answering a support ticket about latency or pricing can resolve the customer's IP through Jentic and use the returned timezone and country to ground its reply. Because the access key sits in the Jentic vault, the agent never sees the credential and the call returns a structured JSON result that is directly usable in subsequent reasoning steps.
Through Jentic, search 'look up ip geolocation', load apiip /api/check/{ip}, and execute with the customer's IP to retrieve country and timezone.
Key Endpoints
3 endpoints — apiip is an ip geolocation service that resolves a single ip, the requester's ip, or a comma-separated batch of up to many ips to detailed location records.
METHOD
PATH
DESCRIPTION
GET
/api/check
Look up the requester's own IP geolocation
GET
/api/check/{ip}
Look up a single IP address
GET
/api/check/{ips}
Look up a comma-separated list of IPs in one call
GET
/api/check
Look up the requester's own IP geolocation
GET
/api/check/{ip}
Look up a single IP address
GET
/api/check/{ips}
Look up a comma-separated list of IPs in one call
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your Apiip accessKey is stored encrypted in the Jentic vault. Agents call the operation via a scoped Jentic key and the accessKey is appended to the query string at execution, so the raw value is never logged or shown to the agent.
Intent-based discovery
Agents search Jentic for 'look up ip geolocation' or 'resolve ip to country' and Jentic returns the apiip.net /api/check operations with their input schemas, including the fields filter.
Time to first call
Direct integration is straightforward but still takes time to wire up the access key, retries, and field selection. Through Jentic an agent can call the lookup in minutes via search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
ipstack
Established IP geolocation API with similar field coverage.
Choose ipstack when you already have apilayer credentials or need its bundled security and currency conversion add-ons.
FAQs
Specific to using Apiip - IP Geolocation API through Jentic.
What authentication does the Apiip API use?
Apiip uses an apiKey passed as the accessKey query parameter on every /api/check request. When called through Jentic, the access key is stored in the Jentic vault and added server-side, so the raw key never appears in the agent's prompt.
Can I look up many IP addresses in a single call?
Yes. Use GET /api/check/{ips} with a comma-separated list of IPs as the path parameter. The response is an array of records, one per input IP, in the same order.
What fields does Apiip return for an IP lookup?
Each record includes ip, countryCode, countryName, regionCode, regionName, city, latitude, longitude, timeZone, currency, and connection metadata. Use the fields query parameter to restrict the response to just the attributes you need.
How do I look up a visitor's country through Jentic?
Search Jentic for 'look up ip geolocation', load the apiip /api/check/{ip} operation, and execute it with the visitor's IP. Jentic returns the country, city, timezone, and currency without exposing the access key to the agent.
What are the rate limits for the Apiip API?
Rate limits are not declared in the OpenAPI spec and depend on your Apiip subscription tier. Monthly request quotas are visible in the Apiip dashboard at apiip.net; treat HTTP 429 as a signal to back off.
GET STARTED