Azure Maps pricing: Local business search API, GET /search/nearby/{format}

Azure Maps's site llms.txt Azure Maps: Local business search API alternatives

Is Azure Maps 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 a Local business search API benchmark yet.This plan is free. We rank 89 plans for Local business search APIs by price. Half the plans cost $0.04 per 1,000 places or less.Stadia Maps's $250 monthly plan is the cheapest paid plan per 1,000 places: $0.001. Stadia Maps charges for each page of results. We count 10 places on each page to get the $0.001 price.

Plan: Gen2 Free one of Azure Maps's 3 plans

Call: GET /search/nearby/{format} one of Azure Maps's 3 calls

API: Local business search API Azure Maps's only API

Local business search 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, Phone, Website, Category, Coordinates.
Nothing to pay. You get 5,000 requests a month, enough for 5,000 pages.
One call. You call GET /search/nearby/{format}. You send lat, lon and format. You set api-version to "1.0". The call returns the businesses there.
Who can get it: anyone with an Azure Maps account. Keep data: with conditions. Use data: with conditions.

Azure Maps: Local business search API alternatives

Azure Maps alternatives: every Local business search API plan compared

The table starts with Azure Maps's cheapest paid plan. Next come plans from other providers with the price per 1,000 places closest to Azure Maps's.

	Azure Maps, pay as you go, Gen2 <500K, GET /search/nearby/{format}	Mapbox, pay as you go, Introductory preview pricing, 50,001 - 500,000 requests, GET /search/searchbox/v1/category/{canonical_category_id}	Amazon Location Service, pay as you go, On-demand, POST /v2/search-text, SearchText (Stored)	Stadia Maps, $20 monthly, Starter, GET /geocoding/v1/search	Amap, CNY 50,000 yearly, 技术服务许可基础版, GET /v5/place/around
$ per 1,000 places	$0.045	$0.04	$0.04	$0.04	$0.05
Completeness	63%	75%	75%	50%	75%
Billing	pay as you go	pay as you go	pay as you go	monthly	yearly
Pay	monthly	monthly	monthly	$20	CNY 50,000
Enough for	as many as you pay for	as many as you pay for	as many as you pay for	50,000 pages a month	500,000 pages a month
Who can get it	anyone with an Azure Maps account	anyone 18 or older	anyone with an AWS account	anyone with a Stadia Maps account	legal entities and organisations that buy Amap's technical service licence, which commercial use of the service needs

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-04.

Product details

The key fields this plan's answer can hold, then each filled column in its row on the sheet.

Address
Phone
Website
Category
Coordinates
Rating, not in the answer
Review count, not in the answer
Opening hours, not in the answer

Price
$ per 1,000 places	$0.00
Per	page of 100
Billing	free

Charges
Most per search	2,000
Also pays for	from the same budget: Get Search POI · Get Search POI Category · Batch Search · Geocode Autocomplete

Not found
$ per 1,000	$0.00

In their words
Their pitch	Use to search for points of interest near a specific location. The Get Search Nearby API is an HTTP GET request most useful for retrieving POI results around a specific location. This endpoint will only return POI results, and does not take in a search query parameter.

Data
Keep data	the validity period indicated in returned headers or 6 months, whichever is shorter
Use data	Customer may not use Azure Maps, or any part thereof (1) to enable turn-by-turn navigation functionality in any Customer Solution or use within an automatic or autonomous vehicle control, or (2) with a vehicle’s dashboard, or a device connected to a vehicles dashboard, systems, or sensors, except that the device may be connected to the vehicle power source for charging purposes. Customer may not use Azure Maps or any part thereof to create a competing database or service, or a derived database populated wholly or partially with Customer’s content and/or content supplied or created by any third party. Customer will not use the content delivered by the Azure Maps in combination with any other third-party database, except that Customer may layer onto the content a type of content not already included within Azure Maps (such as Customer's proprietary content) or which Microsoft separately licenses to Customer. When using content licensed under or subject to an open-source license, Customer may not combine the use of Azure Maps, or any part thereof, in a way that potentially compromises copyright protection. Customer will not modify or create a derivative work based on Azure Maps, or any part thereof, unless expressly permitted to do so under these terms. Microsoft may, in its sole discretion, limit the rate at which Azure Maps, or any portion thereof, may be called. Customer may not cache or store results delivered by the Azure Maps API for the purpose of scaling such Results (as defined below) to serve multiple users, or to circumvent any functionality in Azure Maps, including but not limited to (i) map data tiles, or (ii) information on the calculation of a path between two (2) or more points (“Route”) information (collectively the “Results”). Caching and storing Results and locations (latitude and longitude pair) or addresses that have been returned from a call to Azure Maps (“Geocode”/ ”Reverse Geocode”) are permitted where the purpose of caching is to reduce latency times of the Customer Solution. Results may not be stored for longer than: (i) the validity period indicated in returned headers, or (ii) 6 months, whichever is shorter. However, Customer may store Geocodes as long as Customer maintains an active Azure account. Customer may not display any Results, and/or Azure Maps Weather service results, solely as described in these Terms, on any third-party content or geographical map database. Use of content displaying the TomTom copyright notice must be in accordance with restrictions set forth in the TomTom Licensing Third Party Product Terms and EULA (https://tomtom.com/product-attributions/). Azure Maps may include content that is subject to the Open Data Commons Open Database License ("ODbL"), available at https://opendatacommons.org/licenses/odbl/ or a successor site. Customer’s use of such content is subject to the terms of the ODbL, including the License and Community Guidelines available at https://osmfoundation.org/wiki/Licence/Community_Guidelines, as well as these terms. [...] Customers may not remove, obscure, mask or change any logo and/or copyright notice placed on or automatically generated by Azure Maps. Customer must display in a conspicuous manner within Customer Solution any Microsoft or third-party attribution provided by Microsoft. In addition, customers using the Azure Maps Render services must use the "Get Map Attribution” API to obtain the copyright attribution text and display it in their Customer Solution.

Plan
Pay	$0
You get	5,000 requests a month
Enough for	5,000 pages a month

Rate limit
Per second	500

Speed
Answer	in the call

The call
You send	lat, lon, format, api-version "1.0". Optional: limit, ofs, categorySet, countrySet, radius, language, extendedPostalCodesFor, brandSet, connectorSet, view
Method	GET
Path	/search/nearby/{format}

About the plan
Plan	Gen2 Free
Who can get it	anyone with an Azure Maps account

The 32 fields the plan's answer can hold

name, address, street number, street name, neighborhood, municipality subdivision, municipality, local name, county, tertiary subdivision, state, state name, ZIP code, extended ZIP code, country, country code, country code (ISO 3166-1 alpha-3), latitude, longitude, viewport, entry points, distance, place ID, data source info, phone, website, brands, categories, category IDs, classification code, classification names, total results

Best GTM APIs

All GTM APIs