# IP Geolocation Scraper - Country, City, ISP & ASN (`scrapesage/ip-geolocation-scraper`) Actor

Bulk-look up IP addresses and get clean rows: country, region, city, postal, coordinates, timezone, calling code, ISP, organization and ASN. Two keyless providers with failover. Paste IPs or import thousands from a file. No API key, no browser.

- **URL**: https://apify.com/scrapesage/ip-geolocation-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Other, Agents, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.55 / 1,000 ip looked ups

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## IP Geolocation Scraper - Country, City, ISP & ASN

Bulk-look up **IP addresses** (IPv4 or IPv6) and get clean rows: **country**, **region**, **city**,
**postal**, **coordinates**, **timezone**, **calling code**, **currency**, **ISP**, **organization** and
**ASN**. Two keyless providers with automatic failover. Paste a few IPs or import thousands from a file.
No key, no browser.

### What you get per IP

| Field | Meaning |
|---|---|
| `ip` / `ipType` | The IP and whether it is IPv4/IPv6 |
| `continent` / `country` / `countryCode` / `isEu` | Country data |
| `region` / `city` / `postal` | Sub-country location |
| `latitude` / `longitude` / `timezoneId` | Coordinates and timezone |
| `isp` / `asnOrg` / `asn` / `connectionDomain` | Network: ISP, AS organisation and ASN |
| `callingCode` / `flagEmoji` | Country phone code and flag |

### Input

```json
{ "ips": ["8.8.8.8", "1.1.1.1", "2606:4700:4700::1111"] }
```

- **IP addresses** - one per line (IPv4 or IPv6). **Import from a file** - paste a list, or link a public
  `.txt`/`.csv`, a Google Sheet/Drive link, or an Apify key-value-store record. **Output fields** trim it.

Leave everything empty and the run returns a small free sample so you can see the shape first.

### Reliability

Uses [ipwho.is](https://ipwho.is/) (HTTPS, keyless) as the primary provider and
[ip-api.com](https://ip-api.com/) as a failover - no key, no anti-bot. Invalid IPs are rejected locally
(never billed) and an empty run bills **$0**.

### Honest limits

- **IP geolocation is best-effort, not exact.** City-level accuracy is good for most public IPs but can be
  off (especially for mobile/CGNAT ranges and VPN exit nodes) - that is inherent to IP-to-location data,
  not a scraping gap.
- **Reserved/private IPs** (e.g. 10.x, 192.168.x) return not-found - they have no public geolocation.
- **This is IP intelligence, not WHOIS** - it maps an IP to location/ISP/ASN, not a domain to its registrant.

### Pricing

**$0.001 per IP** on the FREE tier (tiered pricing lowers it with volume). Only resolved IPs are billed;
invalid IPs and empty runs cost nothing.

### Output views

- **IP lookups** - IP, country, region, city, ISP, ASN, coordinates.

### Use with AI assistants (MCP)

Available through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - an agent can
enrich a log of IPs with country/ISP, flag traffic by ASN, or geolocate sign-ups in one call.

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** - AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

# Actor input Schema

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

IPv4 or IPv6 addresses to look up, one per line - e.g. <code>8.8.8.8</code>, <code>2606:4700:4700::1111</code>. <b>Leave empty and the run returns a small free sample.</b>

## `ipsFromFile` (type: `string`):

Bulk-load IP addresses. Either <b>paste the whole list</b> (one per line), or give <b>a single link</b> to a public <code>.txt</code>/<code>.csv</code>, a Google Sheet/Drive link, or an Apify key-value-store record. A file that cannot be read says so and charges nothing.

## `maxItems` (type: `integer`):

Overall cap on saved lookups. You are only charged for IPs actually resolved.

## `outputFields` (type: `array`):

Pick the fields you want and every record is trimmed to exactly those - handy for lean CSV/Sheets exports.

## Actor input object example

```json
{
  "ips": [
    "8.8.8.8",
    "1.1.1.1",
    "208.67.222.222"
  ],
  "maxItems": 100000
}
```

# Actor output Schema

## `results` (type: `string`):

Each record - an IP resolved to country, city, coordinates, ISP and ASN - as a JSON item in the default dataset.

# 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 = {
    "ips": [
        "8.8.8.8",
        "1.1.1.1",
        "208.67.222.222"
    ],
    "ipsFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/ip-geolocation-scraper").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 = {
    "ips": [
        "8.8.8.8",
        "1.1.1.1",
        "208.67.222.222",
    ],
    "ipsFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/ip-geolocation-scraper").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 '{
  "ips": [
    "8.8.8.8",
    "1.1.1.1",
    "208.67.222.222"
  ],
  "ipsFromFile": ""
}' |
apify call scrapesage/ip-geolocation-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/xqkkeLloNIvXwLoJe/builds/tLtVKlgFH4HkAhma3/openapi.json