Bigdatacloud IP Geolocation API

Name: IP Geolocation API
Brand: IP Geolocation API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentAddress ValidationapiKey2 EndpointsREST

For Agents

Resolve an IPv4 address to country, city, network, and connectivity metadata with a confidence score, using BigDataCloud's two geolocation endpoints.

Install Jentic One Beta

Connect the IP Geolocation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 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 | sh

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 instance

Jentic 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 IP Geolocation API.

Resolve an IPv4 address to country, region, and city via /data/ip-geolocation-full

Retrieve ISP, ASN, and BGP network ownership for any IP

Receive a confidence score on each geolocation result through /data/ip-geolocation-with-confidence

GET STARTED

Start building with IP Geolocation API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for IP Geolocation API, keeping it validated and agent-ready. BigDataCloud's IP Geolocation API resolves IPv4 addresses to detailed geographic, network, and confidence metadata using the vendor's next-generation lookup engine, with sub-millisecond response times. The service exposes a full lookup endpoint and a confidence-scored variant, both authenticated by an API key passed as a query parameter. BigDataCloud refreshes geolocation data every two hours and offers 10,000 free queries per month before paid tiers kick in.

Use Cases

Patterns agents use IP Geolocation API for, with concrete tasks.

★ Visitor Geolocation for Personalisation

Web and SaaS products tailor pricing pages, language defaults, and compliance prompts based on the visitor's country and region. The /data/ip-geolocation-full endpoint resolves an IPv4 to country code, city, time zone, and connectivity metadata in a single sub-millisecond call, suitable for inline rendering during page load. The 10,000-query free tier lets a small product run lookups before upgrading at $2 per additional 10K queries.

Call /data/ip-geolocation-full with ip=203.0.113.45 and key={BDC_KEY} and return country.isoAlpha2 and location.city

Fraud Signal Enrichment

Anti-fraud and risk teams enrich each transaction with the ASN, ISP, and confidence-scored location for the originating IP, then feed those signals into a rules engine or ML model. The confidence-scored endpoint /data/ip-geolocation-with-confidence flags results where the underlying data conflicts so the system can downweight uncertain matches. BGP refresh every two hours keeps detections current with hijack and re-routing events.

Call /data/ip-geolocation-with-confidence with ip from a suspect transaction and forward network.organisation, country.isoAlpha2, and confidence to the rules engine

Compliance and Geofencing

Streaming platforms, gambling operators, and SaaS vendors enforce geographic licensing by checking each request's IP against a country and region allowlist. BigDataCloud's geolocation is updated every two hours and includes registry-level ownership, helping reduce false positives for travelers on cellular networks. The 1.0.0 spec supports both IPv4 endpoints over HTTPS at api.bigdatacloud.net.

Call /data/ip-geolocation-full with the request IP and reject if country.isoAlpha2 is not in {US, CA, GB, IE}

Agent-Driven IP Enrichment via Jentic

An AI agent investigating a security alert searches Jentic for 'geolocate an IP address', loads the BigDataCloud full lookup operation, and returns the country, ISP, and confidence in one call. Because the API key is held in Jentic's vault, the agent never sees the secret and the same workflow can be reused across alerts. This makes BigDataCloud usable as a tool inside SOC and triage agents without per-agent key plumbing.

Search Jentic for 'geolocate an IP address', load BigDataCloud /data/ip-geolocation-full, execute with the alert IP, return country and ISP

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for ip geolocation api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/data/ip-geolocation-full

Full IPv4 geolocation with country, city, ISP, ASN

GET

/data/ip-geolocation-with-confidence

Geolocation with a confidence score on the result

GET

/data/ip-geolocation-full

Full IPv4 geolocation with country, city, ISP, ASN

GET

/data/ip-geolocation-with-confidence

Geolocation with a confidence score on the result

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BigDataCloud API keys are stored encrypted in the Jentic vault. Agents receive scoped operation access — the raw key is appended to the `key` query parameter at execution time and never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'geolocate an IP address') and Jentic returns the matching BigDataCloud operation with its parameter schema, so the agent calls the correct endpoint without reading the docs.

Time to first call

Direct BigDataCloud integration: half a day for key handling, parsing, and error retry. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ipstack API

Real-time IP-to-location lookup with bulk endpoint support and IPv6

Choose ipstack when you need IPv6 support or batched lookups in a single call; choose BigDataCloud for sub-millisecond IPv4 with confidence scoring

Alternative

ipgeolocation.io API

Geolocation plus time zone, astronomy, and currency conversion endpoints

Choose ipgeolocation.io when you also need time zone or astronomy data alongside geolocation; choose BigDataCloud when you only need fast geo and ASN data

Alternative

ipapi API

JSON IP location lookup with security and connection-type fields

Choose ipapi when you specifically need proxy/threat detection fields; choose BigDataCloud for sub-millisecond response times and the free 10K monthly tier

FAQs

Specific to using IP Geolocation API through Jentic.

Why is there no official OpenAPI spec for IP Geolocation API?

BigDataCloud does not publish an OpenAPI specification — the IP Geolocation API is documented in narrative form on bigdatacloud.com. Jentic generates and maintains this spec so that AI agents and developers can call IP Geolocation API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the IP Geolocation API use?

The API uses an API key passed as the `key` query parameter on each request. Through Jentic, the BigDataCloud key is stored encrypted in the vault and attached to outbound calls automatically, so the raw key never enters the agent's context.

What does the confidence score on /data/ip-geolocation-with-confidence mean?

The confidence value reflects how well multiple signals (registry, BGP, latency, and historical observations) agree on the returned location. Low scores typically indicate a cellular IP, recently re-allocated address, or a proxy/VPN range — fraud and compliance flows should treat low-confidence matches as soft signals rather than hard ground truth.

What are the rate limits and pricing for the IP Geolocation API?

BigDataCloud provides 10,000 free queries per month, with additional capacity at $2 per extra 10K queries. There is no hard per-second limit published in the spec — for sustained throughput above the free tier you should batch lookups and use the upgraded plan.

How do I geolocate an IP through Jentic?

Run `pip install jentic`, then `await client.search('geolocate an IP address')`, `await client.load(...)` for the BigDataCloud /data/ip-geolocation-full operation, and `await client.execute(...)` with the IP. Jentic injects the API key from the vault and returns the parsed country, city, and network data.

Does the API work for IPv6 addresses?

The 1.0.0 spec exposes only IPv4 lookup endpoints. IPv6 addresses are not supported by /data/ip-geolocation-full or /data/ip-geolocation-with-confidence — for dual-stack workloads, resolve IPv6 traffic to IPv4 upstream or use a complementary provider for v6 ranges.