Location Intelligence — Places & POIs 📍

foXLabs company-intelligence series: Company enrichment · Owler · Craft · Built In · Free lookup · 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

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

{"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.
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
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

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

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['defaultDatasetId']).iterate_items():
    print(item)

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.

❓ FAQ

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? Every run queries the source live, so results are as fresh as the registry.

What place fields are returned? Category, full address, coordinates and place attributes for each matching point of interest.

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
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

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.