Install Jentic One Beta
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.
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 | 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.
What an agent can do with Apiip - IP Geolocation API.
Resolve the caller's own IP to a geolocation record by calling GET /api/check with no ip parameter
Look up a single IPv4 or IPv6 address by passing it in the ip query parameter
Batch-resolve up to 50 comma-separated addresses in one ip parameter, on Apiip's Professional plan
GET STARTED
For Agents
Resolve the requester's IP or any IPv4 or IPv6 address to city, country, and time zone through a single GET /api/check lookup.
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: Resolves IP addresses to location, connection and risk metadata. Does not perform DNS lookups, geocoding of postal addresses, or device fingerprinting.
Jentic publishes the only available OpenAPI specification for Apiip - IP Geolocation API, keeping it validated and agent-ready. Apiip is an IP geolocation service that resolves the requester's own IP, a single IPv4 or IPv6 address, or a comma-separated list of up to 50 addresses to a detailed location record. Every lookup goes through GET /api/check, where an optional ip query parameter selects the target and an accessKey query parameter carries the credential. A record returns city, region, country, postal code, coordinates and ISO codes, plus nested time zone, currency, connection and security objects on the plans that enable those modules. It suits fraud signals, content localization, and routing visitors to the nearest data centre.
Retrieve ISO country and region codes alongside human-readable country and region names for downstream filtering
Read time zone, currency and connection details, which Apiip enables on its Basic plan and above
Read proxy and hosting risk flags from the security object, which Apiip enables on its Professional plan
Restrict the response to named fields with the fields query parameter to reduce payload size
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 or proxy connection, is a useful additional signal alongside device fingerprinting. Apiip returns these fields from GET /api/check, with the connection and security objects available on the plan tiers that enable them.
GET /api/check?ip=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 the currency code, ISO country and time zone in one response, so the frontend can render the right currency symbol and the backend can apply regional tax rules. Apiip enables the currency and time zone modules on its Basic plan and above.
GET /api/check?accessKey=...&fields=currency,countryCode using the visitor's IP from the request to drive localized rendering.
Bulk enrichment of access logs
Enrich web analytics or security logs by passing a comma-separated list of addresses in the ip parameter, up to 50 addresses in one request, 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. Apiip enables the bulk endpoint on its Professional plan.
GET /api/check?ip=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 country and time zone to ground its reply. Because the access key sits in your Jentic One instance, 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 the apiip /api/check lookup, and execute it with the customer's IP to retrieve country and time zone.
3 endpoints — jentic publishes the only available openapi specification for apiip - ip geolocation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/api/check
Look up geolocation for the requester's IP, a single address, or a comma-separated list, selected by the optional ip query parameter
/api/check
Look up geolocation for the requester's IP, a single address, or a comma-separated list, selected by the optional ip query parameter
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your Apiip key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up the location of an IP address', and Jentic returns the matching Apiip operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Alternatives and complements available in the Jentic catalogue.
Specific to using Apiip - IP Geolocation API through Jentic.
Why is there no official OpenAPI spec for Apiip - IP Geolocation API?
Apiip does not publish a machine-readable API description. A probe of apiip.net found no OpenAPI or Swagger document on the site, in its sitemap, or in the JavaScript bundle that carries its reference documentation. Jentic generates and maintains this spec so that AI agents and developers can call Apiip through structured tooling. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the Apiip API use?
Apiip authenticates with an API key sent as the accessKey query parameter, and the spec applies that scheme to the /api/check lookup. Called through Jentic, the key is stored by your own Jentic One instance and added to the request server-side, so it never appears in the agent's prompt.
Can I look up many IP addresses in a single call?
Yes. Pass a comma-separated list of addresses in the ip query parameter of GET /api/check. Apiip documents a limit of 50 values per call, and the response carries one record per address you supply. Apiip enables the bulk lookup on its Professional plan.
What fields does Apiip return for an IP lookup?
A lookup returns ip, countryCode, countryName, regionCode, regionName, city, postalCode, latitude and longitude. Nested objects add connection details such as asn and isp, plus currency, time zone, and a security block whose isProxy flag marks proxy traffic. Use the fields query parameter to restrict the response to the attributes you need. Apiip's own documented response and this spec differ on the casing of a few nested keys, so read them from the response you get rather than assuming one form.
How do I look up a visitor's country through Jentic?
Search Jentic for 'look up ip geolocation', load the apiip /api/check operation, and execute it with the visitor's IP. Jentic returns the country and city without exposing the access key to the agent.
What are the rate limits for the Apiip API?
Apiip limits a single IP address to 100 requests per second and says higher limits are available on request. Monthly volume is set by plan: 1,000 requests on the free plan, 100,000 on Basic and 1,000,000 on Professional. None of this is declared in the OpenAPI spec, so treat HTTP 429 as the signal to back off.
Which response modules does my Apiip plan include?
The free plan returns the location module only. Basic adds the currency, time zone, connection and languages modules; Professional adds the security block and the bulk lookup. If a nested object comes back empty, check your plan before treating the data as missing.
Is there an Apiip MCP server?
You don't need an MCP server to give your agent Apiip. Jentic connects it directly from the API Directory: import Apiip, store your access key once, and your agent can resolve an IP address to a location, with no extra tool definitions loaded into its context.
Can I limit what my agent is allowed to do with the Apiip API?
Yes. Because Jentic One is self-hosted, you decide which Apiip operations your agent may call and which credential it may use. Apiip's surface is read-only geolocation lookup, so the widest access you can grant is a read; you can narrow it further to the single lookup a given agent needs and nothing else.