xMap pricing: Local business search API
Is xMap yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
63% complete: 5 of the 8 key fields we checkSee the 8 fields
$0.00per 1,000 placesWe haven't run xMap through our Local business search API benchmark yet.This plan is free. We rank 239 plans for Local business search APIs by price. Half the plans cost $0.365 per 1,000 places or less.SerpData's $200 pack is the cheapest paid plan per 1,000 places: $0.0004. SerpData charges for each page of results. We count 200 places on each page to get the $0.0004 price.LocationIQ, ScrapeField and TomTom are the best local business search API providers in the Datacircle benchmark.
Plan: Developer one of xMap's 3 plans
Call:
GET / search xMap's only callAPI: Local business search API xMap's only API
About this item
- Freshness. We don't know how fresh this plan's data is.
- 5 of the 8 key fields we check. Address, Category, Coordinates, Rating, Review count.
- Nothing to pay. You get 1,000 credits.
- One call. You call
GET /. Every input is optional:search q,lat,lng,radius_,km filter_,by sort_,by per_,page page,facet_,by max_,facet_ values enrich. The call returns the businesses there. - Anyone can get it. Keep data: 30 days. Use data: with conditions.
xMap: Local business search API alternatives
xMap alternatives: other Local business search API providers by price
We list other providers' plans closest to this plan in price per 1,000 places.
| This planxMap, free | LocationIQ, free | ScrapeField, free | TomTom, free, GET /search/2/categorySearch/{query}.{ext} | Azure Maps, free, Gen2 Free, GET /search/poi/{format} | ValueSERP, free | |
|---|---|---|---|---|---|---|
| $ per 1,000 places | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 | $0.00 |
| Completeness | 63% | 38% | 100% | 75% | 75% | 0% |
| Billing | free | free | free | free | free | free |
| Pay | $0 | $0 | $0 | $0 | $0 | $0 |
| Enough for | not published | 5,000 pages a day | about 666 pages | 2,500 pages a month | 5,000 pages a month | 100 pages |
| Freshness | unknown | unknown | 24 hours | unknown | unknown | live |
| Who can get it | anyone | anyone | anyone who verifies an email | anyone not barred from receiving the Licensed Products under the laws of the United States or other countries | anyone with an Azure Maps account | anyone |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-06.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Address
- Phone, not in the answer
- Website, not in the answer
- Category
- Coordinates
- Rating
- Review count
- Opening hours, not in the answer
| $ per 1,000 places | $0.00 |
|---|---|
| Billing | free |
| $ per 1,000 | $0.00 |
|---|
| Their pitch | 24M+ US locations with 30+ fields per record. Verified, deduplicated, updated monthly. Query by name, category, bounding box, or radius. Built for agents. |
|---|
| Keep data | 30 days |
|---|---|
| Use data | Use POI Data returned by the Service internally within Customer's own applications, analytics, products, and business operations. Display POI Data to Customer's end users as part of a value-added application or interface (e.g. a map, dashboard, or AI agent response) where POI Data is one component of a larger offering. [...] Customer may not, and may not permit any third party to: Resell, sublicense, rent, lease, or otherwise distribute POI Data as a standalone product or substantially-unchanged dataset. Publish POI Data in bulk (CSV, JSON, database dumps, screenshots, etc.) on any public, semi-public, or customer-accessible channel. Transfer POI Data to any third party except Customer's end users viewing it inside Customer's own application as permitted by §3. Use the Service to reconstruct, recreate, or approximate a competing POI dataset, whether for internal use, resale, or open-sourcing. Systematically cache, download, or enumerate the full dataset or any material portion of it (see §4.5 for caching limits). Use POI Data as training data, fine-tuning data, or embedding source for any machine learning model intended to predict, reproduce, or substitute for POI Data. Use POI Data to train any generative AI model that will output POI Data back to users (whether Customer's users, end users, or the public). Create multiple accounts to circumvent quotas, free-tier limits, or rate limits. Share API keys across organizations or with third parties. Bypass, reverse engineer, probe, or attempt to disable any security, rate-limit, billing, or metering mechanism. [...] Not use the cache to build a persistent derivative dataset. |
| Pay | $0 |
|---|---|
| You get | 1,000 credits |
| Per second | 5 |
|---|---|
| Batch | 1 |
| Answer | in the call |
|---|
| You send | nothing required. Optional: q, lat, lng, radius_km, filter_by, sort_by, per_page, page, facet_by, max_facet_values, enrich |
|---|---|
| Method | GET |
| Path | /search |
| Plan | Developer |
|---|---|
| Who can get it | anyone |
The 14 fields the plan's answer can hold
name, category, city, state, ZIP code, business status, chain, brand name, rating, review count, price level, traffic bucket, latitude, longitude