IPstack API
Browse all Ipstack APIs✓ Official Vendor SpecData EnrichmentAddress ValidationapiKey3 EndpointsREST
For Agents
Resolve any IPv4 or IPv6 address — including the caller's own — to country, city, ASN, currency, time zone, and proxy/VPN risk signals. Supports up to 50 IPs in a single bulk lookup.
Use for: Find the country and city of an IPv4 address, Get the geolocation of the user calling my service, Look up the time zone associated with an IP, Check whether an incoming IP is a known VPN or proxy
Not supported: Does not handle reverse DNS, hostname-to-IP resolution, or domain WHOIS — use for IP-address geolocation and risk enrichment only.
IPstack is a real-time IP geolocation service that resolves IPv4 and IPv6 addresses to country, region, city, ZIP, latitude/longitude, time zone, currency, connection type, and security signals. The HTTP API exposes three endpoints: /check for the requester's own IP, /{ip} for a single address, and /{ips} for bulk lookups of up to 50 comma-separated IPs. All requests authenticate with an access key passed as a query parameter and return JSON.
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://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 IPstack API.
Geolocate any IPv4 or IPv6 address to city, region, country, and coordinates
Detect the requester's own IP and its location through the /check endpoint
Look up up to 50 IPs in a single bulk request with comma-separated input
Retrieve time zone, currency, and language metadata tied to an IP location
Identify VPN, proxy, Tor, and crawler traffic through the security module
Resolve ASN, ISP, and connection type for traffic analysis
Use Cases
Patterns agents use IPstack API for, with concrete tasks.
★ Country-Aware Content and Pricing
Personalize landing pages, currency, and tax calculations from the visitor's IP without prompting for browser geolocation. The /check endpoint resolves the caller's IP server-side, returning country code and currency in one call. Integration is typically a single afternoon for a SaaS or storefront.
Call GET /check with the access_key query parameter and use country_code and currency.code to set the visitor's locale and pricing.
Checkout Fraud Filtering
Reduce chargebacks by checking each buyer's IP for VPN, proxy, or Tor flags and comparing IP country with billing country. IPstack's security module returns proxy, tor, threat_level, and threat_types fields when enabled, supporting rule-based decline or step-up authentication. Adds milliseconds to checkout latency.
Call GET /{ip} for the buyer's IP with security parameters enabled and decline the order if security.proxy is true or threat_level is high.
Bulk Log Enrichment
Enrich large batches of IPs from web server logs, application telemetry, or threat feeds in a single network round-trip. The /{ips} bulk endpoint accepts up to 50 comma-separated addresses and returns an array of fully-enriched records, ideal for batched analytics pipelines.
Send GET /{ips} with up to 50 comma-separated IPs from the latest log batch and write each result row to the analytics warehouse.
Agent IP Lookup via Jentic
An AI agent triaging support tickets or fraud reviews can resolve any IP to country, ISP, and risk signals through Jentic without browsing IPstack docs. Jentic exposes the three endpoints by intent and injects the access key at execution.
Use Jentic to search for 'look up the location of an IP address', load the standard /{ip} operation, and execute it with the IP from the support ticket.
Key Endpoints
3 endpoints — ipstack is a real-time ip geolocation service that resolves ipv4 and ipv6 addresses to country, region, city, zip, latitude/longitude, time zone, currency, connection type, and security signals.
METHOD
PATH
DESCRIPTION
GET
/check
Resolve the requester's own IP address
GET
/{ip}
Standard lookup for a single IPv4 or IPv6 address
GET
/{ips}
Bulk lookup for up to 50 comma-separated IPs
GET
/check
Resolve the requester's own IP address
GET
/{ip}
Standard lookup for a single IPv4 or IPv6 address
GET
/{ips}
Bulk lookup for up to 50 comma-separated IPs
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The IPstack access_key is stored encrypted in the Jentic vault and appended to the query string at execution time, so the secret never enters the agent's prompt context or logs.
Intent-based discovery
Agents search by intent (e.g. 'find the country of an IP') and Jentic returns the matching IPstack operation with its parameter schema, so the model fills in the IP and executes the call.
Time to first call
Direct IPstack integration: 1-2 hours for HTTP client and key handling. Through Jentic: under 10 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
ipapi - IP Geolocation API
Sister product with the same endpoint shape and access_key auth.
Choose ipapi if you already have an ipapi subscription; the operation surface is identical.
FAQs
Specific to using IPstack API through Jentic.
What authentication does the IPstack API use?
IPstack uses an access_key query parameter on every request. Through Jentic, the access key is stored in the encrypted vault and injected at execution time, so the agent never sees the raw secret.
Can I look up multiple IP addresses in one IPstack call?
Yes. The GET /{ips} endpoint accepts up to 50 comma-separated IPv4 or IPv6 addresses and returns a JSON array of enriched results in a single response.
Does IPstack detect VPN and proxy traffic?
Yes, when the security module is enabled on your plan. The /{ip} and /{ips} responses include a security object with proxy, tor, threat_level, and threat_types fields suited to fraud scoring.
What are the rate limits for the IPstack API?
Limits are tied to plan: the free tier allows 100 requests per month, while paid tiers scale from 50,000 to several million requests monthly. The API enforces monthly quotas rather than per-second caps.
How do I geolocate the caller's own IP through Jentic?
Search Jentic for 'detect my own IP location', load the GET /check operation, and execute. Jentic injects access_key and returns the parsed JSON with country, city, and coordinates.
Does IPstack work with IPv6 addresses?
Yes. Both the standard /{ip} and bulk /{ips} endpoints accept IPv6 inputs and return the same enriched fields, including coordinates, ASN, and time zone.
GET STARTED