# Location Intelligence — 76M Global POIs (Overture Maps) (`foxlabs/location-intelligence`) Actor

Search ~76M points of interest worldwide from Overture Maps by area (point+radius or bounding box). Name, category, brand, phone, email, website, socials, full address & exact coordinates. Official open data, commercial reuse permitted. No API key.

- **URL**: https://apify.com/foxlabs/location-intelligence.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 6 total users, 2 monthly users, 88.9% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Location Intelligence — Places & POIs 📍

**foXLabs company-intelligence series:** [Company enrichment](https://apify.com/foxlabs/company-enrichment) · [Owler](https://apify.com/foxlabs/owler-intelligence) · [Craft](https://apify.com/foxlabs/craft-intelligence) · [Built In](https://apify.com/foxlabs/builtin-intelligence) · [Free lookup](https://apify.com/foxlabs/company-lookup-free) · [VC & investor watchlist](https://apify.com/foxlabs/vc-investor-watchlist)

🎉 Turn places data into clean, structured location intelligence — no login, no API key, one row per place, with the category, address, coordinates and attributes.
Built for retail, field sales and market-expansion teams.

### 🔍 What is the Location Intelligence — and when should you use it?

Give this actor place names, categories or locations and it returns matching places from public places / points-of-interest data — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

**Use it when you need:** a company list for outreach; a quick profile before a call; or a starting point for account research.

**Use something else when:** you need company firmographics — this is places/POI data, not a company registry.

### 🤖 Use with AI agents

**Already on the Apify MCP server?** Ask for this Actor by name: `foxlabs/location-intelligence`.

**Your agent can pay for its own runs.** This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over **x402 (USDC on Base)** or **Skyfire** — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

```
I want to pull place company records using the Apify Actor `foxlabs/location-intelligence`.
Input: `location`, `boundingBox`, `category`, `nameQuery` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"location":{"latitude":19.4326,"longitude":-99.1332,"radiusKm":2},"maxResults":500}
Ask me what to look up, run the Actor, then summarise the rows as a table.
```

The machine-readable API, MCP config and OpenAPI definition live at `apify.com/foxlabs/location-intelligence.md`.

### 📋 Overview

Everything you need to turn public places / points-of-interest data into clean, structured data — in one actor, with no login, cookies or API key.

**Why teams pick this actor:**

- ✅ **Whole source, one call** — name or ID in, matching places out.
- 🧹 **No empty-promise columns** — only fields this registry actually fills; degenerate columns are removed.
- 🔗 **Stable identifiers** — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
- 💰 **Per-row pricing** — a minimal price per delivered row, no subscription.
- 🤖 **Agent-ready** — MCP + x402 agentic payments.

### ✨ Features

- 🔍 **Name or ID lookup** — relevance-ranked name search or exact registry-ID lookup.
- 🏢 **Full entity profile** — status, legal form, formation date, address and the registry’s own contact fields.
- 🧹 **Clean schema** — deduplicated camelCase rows, ready for CSV/Excel/JSON.

### 🎬 Quick Start

```bash
curl -X POST "https://api.apify.com/v2/acts/foxlabs~location-intelligence/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"location":{"latitude":19.4326,"longitude":-99.1332,"radiusKm":2},"maxResults":500}'
```

### 🚀 Getting Started (3 steps)

1. **Choose your targets** — place names, categories or locations.
2. **Set the cap** — `maxResults` limits how many results are returned.
3. **Run and export** — get a clean dataset as JSON, CSV or Excel.

### 📥 Input

```json
{"location":{"latitude":19.4326,"longitude":-99.1332,"radiusKm":2},"maxResults":500}
```

| Field | Type | Description |
|---|---|---|
| `location` | object | Search around a point: { "latitude": 19.4326, "longitude": -99.1332, "radiusKm": 2 }. The simplest way to pull every place in an area. |
| `boundingBox` | object | Alternative to point+radius: an explicit box { "minLatitude", "minLongitude", "maxLatitude", "maxLongitude" }. |
| `category` | string | Filter by place category, e.g. "restaurant", "hotel", "pharmacy", "gym". Case-insensitive match on the place's primary Overture category. |
| `nameQuery` | string | Only places whose name contains this text, e.g. "Starbucks", "Oxxo". Great for mapping a brand's footprint. |
| `country` | string | Restrict to a country by 2-letter ISO code, e.g. "MX", "US", "DE". |
| `onlyWithContact` | boolean | Return only places that have a phone, email, website or social profile — ideal for lead lists. |
| `onlyOpen` | boolean | Leave out places Overture marks as **permanently closed**. Places whose status Overture does not state are kept, because the status is missing in whole countries (measured: 72% of New York places carry a status, almost none in Istanbul). |
| `maxResults` | integer | Maximum number of places to return (1–50000). A dense urban area can hold thousands. |
| `release` | string | Advanced: pin a specific Overture Maps release (e.g. "2026-08-19.0"). Leave blank to use the newest release Overture currently publishes. Overture keeps only the… |

### 📤 Output

One row per result, saved to the dataset. Every row carries `scrapedAt`. Lookups that cannot be completed are reported in the run log rather than silently dropped.

| Field | Description |
|---|---|
| `id` | Id |
| `name` | Name |
| `category` | Category |
| `alternateCategories` | Alternate Categories |
| `categoryPath` | Overture's category path from coarse to fine, e.g. `["eat_and_drink","restaurant","turkish_restaurant"]` (new in the 2026-09-23 release) |
| `basicCategory` | Overture's coarse category bucket |
| `operatingStatus` | `open`, `permanently_closed`, or `null` where Overture does not say |
| `brand` | Brand name where the place belongs to one |
| `email` | Email |
| `confidence` | Confidence |
| `phone` | Phone |
| `website` | Website |
| `socials` | Socials |
| `hasContact` | Has Contact |
| `contactMethods` | Contact Methods |
| `address` | Principal address |
| `city` | City |
| `region` | Region |
| `postcode` | Postcode |
| `country` | Country |
| `latitude` | Latitude |
| `longitude` | Longitude |
| `source` | Source |
| `license` | License |

### 💼 Use cases

**1. Territory planning** — map places by category in an area.
*Input:* a category + location. *Output:* places + coordinates. *Use:* a coverage map.

**2. Retail expansion** — find candidate locations.
*Input:* categories + locations. *Output:* places + attributes. *Use:* a site shortlist.

**3. Field-sales routing** — build a POI list for a territory.
*Input:* categories. *Output:* places + addresses. *Use:* a call list.

### 🔗 Integration

**JavaScript / Node.js**

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/location-intelligence').call({"location":{"latitude":19.4326,"longitude":-99.1332,"radiusKm":2},"maxResults":500});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);
```

**Python**

```python
from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/location-intelligence').call(run_input={"location":{"latitude":19.4326,"longitude":-99.1332,"radiusKm":2},"maxResults":500})
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)
```

Written for `apify-client` 3 for Python, where `call()` returns a run object; with version 1 or 2 it returns a dict — write `run['defaultDatasetId']` there.

**Automation (n8n / Zapier / Make):** schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

### 📊 Pricing

Pay-per-event: **per delivered record**. Empty or failed lookups are never billed. [View current pricing.](https://apify.com/foxlabs/location-intelligence)

### ❓ FAQ

#### How is billing calculated?

Pay per result: you are charged only for places actually returned, never for an empty run or an error.

#### Is it legal to use this data?

It reads publicly available business and place information. It collects no private personal data and requires no login. Use the output in line with applicable laws and the terms of the sources.

#### Do I need an account, login or API key?

No. This reads public places / points-of-interest data.

#### What do I search by?

Place names, categories or locations.

#### How current is the data?

Overture publishes its places data as a monthly release, and every run reads the **newest release Overture currently serves** (the Actor looks the releases up at run time, so it never asks for one that has been taken offline). The run log prints which release the rows came from, and each row carries it in `source`. Pin an older one with `release` if you need a repeatable snapshot.

#### What place fields are returned?

Category, full address, coordinates and place attributes for each matching point of interest.

#### Do you deliver businesses that have closed?

Overture marks some places `permanently_closed` (26,374 of them in the New York area alone). Those rows carry `operatingStatus: "permanently_closed"`, and `onlyOpen: true` leaves them out. In countries where Overture states no status the field is `null` and nothing is filtered — the Actor never guesses that a place is open.

#### Can I export to CSV / Excel / JSON?

Yes — directly from the Apify dataset.

### 🐛 Troubleshooting

- **Fewer rows than expected** — raise `maxResults`, or refine the input.
- **A name returns an unexpected entity** — it matched a similar registered name; search the exact registry ID.
- **No rows for a name** — try the entity’s exact legal name or its registry ID.

### ⚖️ Is it legal to scrape this data?

This actor reads publicly available places / points-of-interest data. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

### 🤝 Support & contact

- 🌐 **Website:** [data.foxlabs.com.tr](https://data.foxlabs.com.tr)
- 📧 **Email:** info@foxlabs.com.tr
- 🐛 **Issues:** open a ticket in the Actor’s **Issues** tab
- 🧰 **More clean B2B data actors:** [Fox Labs on Apify](https://apify.com/foxlabs)

### Changelog

#### 0.1.16 — 2026-10-21 — fixed: Overture renamed its category columns

- Overture's 2026-09-23 release renamed `categories{primary, alternate}` to `taxonomy{primary, hierarchy, alternates}`. The query was written for the old names, so every run on the new release failed with a binder error — which is what put this Actor under maintenance. The Actor now reads each release's own column list and builds the query from it, so old and new releases both work.
- **New columns:** `categoryPath` (the category path from coarse to fine), `basicCategory` and `operatingStatus` (`open` / `permanently_closed` where Overture states it).
- **New input `onlyOpen`:** leave out places marked permanently closed; places with no stated status are kept.
- The FAQ no longer says the data is "as fresh as the registry": Overture publishes monthly releases and the Actor reads the newest one it serves.

#### 0.1.15 — 2026-10-08 — README: the Python example works with the current Apify client

- The README's Python example read the results with `run['defaultDatasetId']`. With the current Apify client for Python (version 3) `call()` returns a run object, not a dict, and that line raised `TypeError: 'Run' object is not subscriptable` — after the run itself had finished. The example now reads `run.default_dataset_id`; with client version 1 or 2, keep `run['defaultDatasetId']`. Checked with apify-client 3.2.1, 2.5.1 and 1.12.2.
- No code, output field or pricing change.

#### 0.1.14 — 2026-09-20 — README examples corrected against the real input schema

- **The README's code examples did not match this Actor.** They used `queries` and `maxResultsPerQuery` — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: `{"location":{"latitude":19.4326,"longitude":-99.1332,"radiusKm":2},"maxResults":500}`
- The input table is regenerated from `input_schema.json`, so it lists the fields the Actor actually accepts.
- Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries `query`", and `industry` described as a NACE code.
- No code, output field or pricing change.

#### 0.1 — 2026-09-07

- **Dropped empty-promise columns.** Removed `brand, email` — public places / points-of-interest data does not carry them, so they were shipped as always-null columns. Only fields this source actually fills are now emitted.
- **Enabled AI-agent payments (x402) + rebuilt the README to the full standard** (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

#### 0.0

- Initial release: data from public places / points-of-interest data by name or registry ID.

# Changelog

This Actor's version history is a separate document: https://apify.com/foxlabs/location-intelligence/changelog.md

# Actor input Schema

## `location` (type: `object`):

Search around a point: { "latitude": 19.4326, "longitude": -99.1332, "radiusKm": 2 }. The simplest way to pull every place in an area.

## `boundingBox` (type: `object`):

Alternative to point+radius: an explicit box { "minLatitude", "minLongitude", "maxLatitude", "maxLongitude" }.

## `category` (type: `string`):

Filter by place category, e.g. "restaurant", "hotel", "pharmacy", "gym". Case-insensitive match on the place's primary Overture category.

## `nameQuery` (type: `string`):

Only places whose name contains this text, e.g. "Starbucks", "Oxxo". Great for mapping a brand's footprint.

## `country` (type: `string`):

Restrict to a country by 2-letter ISO code, e.g. "MX", "US", "DE".

## `onlyWithContact` (type: `boolean`):

Return only places that have a phone, email, website or social profile — ideal for lead lists.

## `onlyOpen` (type: `boolean`):

Deliver only places Overture does not mark as permanently closed. Places whose status Overture does not state are kept (the status is missing in many countries), so this filter removes known-closed places, not unknown ones.

## `maxResults` (type: `integer`):

Maximum number of places to return (1–50000). A dense urban area can hold thousands.

## `release` (type: `string`):

Advanced: pin a specific Overture Maps release (e.g. "2026-08-19.0"). Leave blank to use the newest release Overture currently publishes. Overture keeps only the newest couple of releases online, so an old pin stops resolving once it is rotated out.

## Actor input object example

```json
{
  "location": {
    "latitude": 19.4326,
    "longitude": -99.1332,
    "radiusKm": 2
  },
  "category": "restaurant",
  "country": "",
  "onlyWithContact": false,
  "onlyOpen": false,
  "maxResults": 500
}
```

# Actor output Schema

## `dataset` (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 = {
    "location": {
        "latitude": 19.4326,
        "longitude": -99.1332,
        "radiusKm": 2
    },
    "category": "restaurant",
    "country": "",
    "maxResults": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/location-intelligence").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 = {
    "location": {
        "latitude": 19.4326,
        "longitude": -99.1332,
        "radiusKm": 2,
    },
    "category": "restaurant",
    "country": "",
    "maxResults": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("foxlabs/location-intelligence").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 '{
  "location": {
    "latitude": 19.4326,
    "longitude": -99.1332,
    "radiusKm": 2
  },
  "category": "restaurant",
  "country": "",
  "maxResults": 500
}' |
apify call foxlabs/location-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foxlabs/location-intelligence"
        }
    }
}
```

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/qrGOmjFrd0yjaKU2f/builds/NPGfzbetRHPw6XVGH/openapi.json