# IP Geolocation API — city, ISP & timezone (no key) (`synthetic.ia/ip-geolocation-api`) Actor

Geolocate any IP address or hostname: city, region, country, latitude/longitude, ISP, ASN/organization and timezone. Single or batch (up to 25). ipwho.is with an ip-api fallback. Clean HTTP API + MCP, no key. Pay per query.

- **URL**: https://apify.com/synthetic.ia/ip-geolocation-api.md
- **Developed by:** [Synthetic](https://apify.com/synthetic.ia) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 geolocation queries

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## IP Geolocation API — city, ISP & timezone (no key)

Turn an **IP address** (or a **hostname**) into a location, behind a clean HTTP API (and MCP tool): **city, region, country, latitude/longitude, postal code, ISP, ASN/organization** and **timezone** — one at a time or in **batches** of up to 25. Perfect for analytics, fraud/risk signals, personalization, logs enrichment and agents. **No API key.** Pay per query.

- 📍 **Precise location** — city, region, country (+ code), continent, EU flag, postal code, lat/lon.
- 🛰️ **Network** — ISP, organization and **ASN** for the IP.
- 🕒 **Timezone** — IANA timezone id, UTC offset and current local time.
- 📦 **Batch** — geolocate up to 25 IPs/hostnames in a single call.
- 🔁 **Resilient** — ipwho.is over HTTPS with an automatic ip-api fallback.
- 💵 Pay per query · no key.

### The use case it was built for

Enrich a request log with country + city, gate content by region, flag a suspicious sign-in from an unexpected ASN, or let an agent answer "where is this IP?". Clean, typed JSON — no key, no SDK.

### Sample output (`lookup`, ip "8.8.8.8")

```json
{
  "ok": true, "query": "8.8.8.8", "ip": "8.8.8.8", "type": "IPv4",
  "city": "San Jose", "region": "California", "country": "United States", "countryCode": "US",
  "latitude": 37.3394, "longitude": -121.895, "postal": "95025",
  "asn": 15169, "org": "Google LLC", "isp": "Google LLC",
  "timezone": "America/Los_Angeles", "flag": "🇺🇸", "provider": "ipwho.is"
}
```

### How to use

- **HTTP API (Standby):** POST or GET `/lookup`, `/batch`. `GET /` returns help. Example: `GET /lookup?ip=1.1.1.1`.
- **Normal run:** pass `{ operation, ip | ips }`; results land in the dataset + key-value store.
- **MCP tool:** expose it to your agent via Apify's MCP server.

### Input

- **operation** — `lookup` · `batch`.
- **ip** — an IPv4/IPv6 address or a hostname (for `lookup`).
- **ips** — an array (or comma-separated list) of up to 25 targets (for `batch`).

### Pricing

**Per query** from **$0.004** (down to $0.001 on higher tiers). A single lookup and a full batch of 25 each count as **one** query.

### Related Actors

- **[Domain & DNS Lookup](https://apify.com/synthetic.ia/domain-dns-lookup)** — DNS records, whois and IP-network ownership.
- **[Open-Meteo Weather](https://apify.com/synthetic.ia/open-meteo-weather)** — forecast & history by city or coordinates.

### FAQ

**Do I need a key?** No.

**IP or hostname?** Both — a hostname is resolved to its IP and then geolocated.

**How accurate is the city?** IP geolocation is approximate (typically city/region level) and depends on the provider's database; it is not GPS.

### Notes & limits

Uses ipwho.is (primary, HTTPS) and ip-api.com (fallback). Private/reserved IPs cannot be geolocated and return a clear error. Batch is capped at 25 targets per call.

# Changelog

This Actor's version history is a separate document: https://apify.com/synthetic.ia/ip-geolocation-api/changelog.md

# Actor input Schema

## `operation` (type: `string`):

Geolocate one target or many.

## `ip` (type: `string`):

An IPv4/IPv6 address or a hostname, e.g. 8.8.8.8 or github.com.

## `ips` (type: `array`):

Up to 25 IPs or hostnames to geolocate at once.

## Actor input object example

```json
{
  "operation": "lookup",
  "ip": "8.8.8.8",
  "ips": []
}
```

# Actor output Schema

## `result` (type: `string`):

No description

## `runs` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "ip": "8.8.8.8"
};

// Run the Actor and wait for it to finish
const run = await client.actor("synthetic.ia/ip-geolocation-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "ip": "8.8.8.8" }

# Run the Actor and wait for it to finish
run = client.actor("synthetic.ia/ip-geolocation-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "ip": "8.8.8.8"
}' |
apify call synthetic.ia/ip-geolocation-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,synthetic.ia/ip-geolocation-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vzTR0c1RF0RZ2iO2f/builds/1jnrEDBoMknGbYZIS/openapi.json