IPstack API
Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey3 EndpointsREST
For Agents
Resolve any IP address to geolocation, connection, and security data, one at a time or in bulk, and read the requester's own IP.
Use for: I need to find the country and city for a visitor's IP address, Look up the timezone for an IP so I can localize a response, Check whether an incoming IP is a proxy or VPN before allowing access, Give me latitude and longitude for a list of IP addresses
Not supported: Does not handle address geocoding, routing, or mapping tiles; use it for IP-based geolocation and connection lookups only.
The IPstack API resolves an IP address into location, timezone, currency, connection, and security details. It covers single-address lookups, bulk lists of addresses, and a check on the requester's own IP, returning latitude, longitude, region, and country data for each address. Responses arrive as JSON scoped to the fields you request, so an agent can localize content, route traffic, or flag risky connections from one call.
Install Jentic One Beta
Connect the IPstack API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IPstack 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fipstack.com%2Fipstack" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fipstack.com%2Fipstack" | 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 IPstack API.
Resolve a single IP address to city, region, country, and coordinates
Look up geolocation for many IP addresses in one bulk request
Detect the caller's own public IP and its location
Read connection metadata such as autonomous system number, ISP, and connection type
Flag proxy, VPN, Tor, and crawler traffic through the security module
Return timezone and currency details tied to an IP's location
Use Cases
Patterns agents use IPstack API for, with concrete tasks.
★ Localize content by visitor IP
Websites and applications often tailor language, currency, and offers to a visitor's location. The IPstack API turns an incoming IP address into country, region, city, timezone, and currency fields in a single lookup, so an application can pick the right locale before the first page renders. The location is approximate and derived from IP registries, suitable for personalization rather than legal or billing addresses.
Look up the country, currency, and timezone for a visitor's IP address and select the matching locale settings.
Screen risky traffic
Fraud and abuse teams need to know whether a request comes from an anonymizing network. The IPstack security module reports proxy, VPN, Tor, and crawler flags alongside a threat level for an IP address, letting a service add verification or block access before completing a sensitive action. Coverage depends on the subscription tier that enables the security fields.
Check an IP address against the security module and decide whether to require extra verification when a proxy or Tor exit node is detected.
Bulk-enrich stored IP logs
Analytics and CRM pipelines accumulate raw IP addresses that become useful once resolved to geography. The IPstack bulk lookup accepts a comma-separated list of addresses and returns location and connection data for each, so a batch job can append country and ISP columns to event or contact records. Bulk lookups are available on paid plans.
Submit a list of IP addresses from the last day of logs and attach the returned country and ISP fields to each event record.
Agent-driven location enrichment
An AI agent handling support or onboarding can resolve a user's IP to add geographic context to its reasoning. Through Jentic the agent discovers the IPstack lookup by intent, calls it with the address in question, and reads back the location and connection fields it needs, without the developer wiring the request by hand. The agent only ever sees the resolved fields, never the account credential.
Resolve the end user's IP address to city and country and add that context to the agent's session before answering a location-sensitive question.
Key Endpoints
3 endpoints — the ipstack api resolves an ip address into location, timezone, currency, connection, and security details.
METHOD
PATH
DESCRIPTION
GET
/check
Look up location and connection data for the IP address that made the request.
GET
/{ip}
Resolve a single IP address to location, connection, timezone, currency, and security fields.
GET
/{ips}
Resolve a comma-separated list of IP addresses in one bulk request.
GET
/check
Look up location and connection data for the IP address that made the request.
GET
/{ip}
Resolve a single IP address to location, connection, timezone, currency, and security fields.
GET
/{ips}
Resolve a comma-separated list of IP addresses in one bulk request.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring IPstack yourself means appending an access key to every query string, handling its single global host, and parsing only the response modules you enabled. With Jentic you install once, import IPstack from the API Directory, and store the access key a single time.
Permission scoping
Jentic lets you grant your agent only the IPstack operations it needs, such as single-address lookups without bulk queries, and enforces that on every call.
Credential isolation
Your IPstack access key is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents find IPstack through Jentic's intent search, matching a request like 'geolocate this IP address' to the right lookup operation without hardcoded endpoints.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using IPstack API through Jentic.
What can an AI agent do with the IPstack API through Jentic?
An agent can resolve any IP address to location, timezone, currency, connection, and security fields, look up many addresses in one bulk call, and read the IP that made the request. Through Jentic the agent finds these operations by intent and calls them with your stored credential injected at run time.
How do I authenticate with the IPstack API?
IPstack uses an API access key passed as the `access_key` query parameter on every request. You store that key once in your Jentic One instance, and it is attached to each call at execution time rather than placed in the agent's prompt.
Is the location data accurate enough for billing or legal addresses?
No. IPstack derives location from IP registry data, so results are approximate at the city level and can be wrong for mobile or proxied traffic. Use it for personalization, routing, and risk signals, not for verified billing or legal addresses.
Does IPstack publish rate limits or request quotas?
The OpenAPI specification does not state rate limits or monthly quotas; those depend on your IPstack subscription tier. Check your current allowances in the IPstack dashboard and documentation at https://ipstack.com/documentation.
Can I limit what my agent is allowed to do with the IPstack API?
Yes. IPstack is a read-only lookup API, and Jentic lets you allow only the specific operations your agent needs, such as single-IP lookups while withholding bulk queries. Your Jentic One instance enforces that boundary on every call, and the credential stays outside the agent's context.
GET STARTED