Yelp Places API vs Azure Maps Search for AI agents
Yelp Places API is Yelp's licensed API (formerly Yelp Fusion) for searching businesses and reading Yelp business details, ratings, photos and review excerpts. Azure Maps Search is Microsoft Azure's location search service for geocoding and finding places and businesses by name or category.
The short answer
- Yelp Places API: Yelp ratings, review excerpts and photos for restaurants and local services in consumer apps that display Yelp content. The terms rule out passing that content to an LLM.
- Azure Maps Search: Teams already on Azure who want place search billed on their Azure account under Microsoft's enterprise terms.
Side by side
| Yelp Places API | Azure Maps Search | |
|---|---|---|
| Searches | Local businesses listed on Yelp. Yelp says it covers "millions of businesses around the world," and the supported-locales page lists 32 countries. | Addresses, places and businesses by name or category. Search v1.0 (POI, category, nearby search) is superseded by Search 2026-01-01 but still works. |
| Returns | JSON over REST at https://api.yelp.com/v3. Results include name, address, phone, Yelp rating, price level, review count, coordinates, categories, image and Yelp URL. Photos and review excerpts depend on the plan. | JSON. Search v1 POI results include name, phone, url, categories, brands and optional opening hours. |
| Before the first call | A Yelp developer account (a business email is required for the trial) and a private API key. Paid plans need a credit card on file. | An Azure subscription with an Azure Maps account. Authentication is by Shared Key, Microsoft Entra ID or SAS token. |
| Free | A 30-day trial with up to 5,000 API calls, for evaluation only, not commercial use. There is no permanent free tier. | 5,000 Search transactions a month. |
| Paid | Base costs $229 a month plus $5.91 per extra 1,000 calls. Enhanced costs $299 a month plus $6.57 per 1,000. Premium costs $643 a month plus $14.13 per 1,000. The FAQ says paid plans include 30,000 calls a month by default. | $4.50 per 1,000 Search transactions (under 500K a month). Volume discounts start at 100,000 transactions. |
| Acting on a result | Results include the business phone number and its Yelp page URL. There is no way to message a business through the Places API. | v1 POI results include phone and website URL. There is no way to message a business through the API. |
| Limits on keeping or showing results | No caching or storing of Yelp Content for more than 24 hours. No building your own business-listing database from it. Display Requirements apply, and Yelp can require removal of content within 24 hours. | Results may be cached only to reduce latency, not to serve multiple users, and for no longer than the header validity or 6 months, whichever is shorter. Geocodes may be kept while the Azure account is active. Results may not be displayed on third-party maps or content. |
| AI in its terms | Very restrictive. Section 9 bans training or fine-tuning generative AI models on Yelp Content. Section 9.4 bans submitting or ingesting any Yelp Content into any Generative AI Model, for example in prompts to ChatGPT. Yelp sells a separate Yelp AI API for conversational use at $25 per 1,000 calls. | The Product Terms say the customer may not modify or create a derivative work from any content using machine learning or artificial intelligence unless the terms expressly allow it. They also forbid building a competing or derived database. |
| Coverage | 32 countries in Yelp's supported-locales list, including the US. | Not stated on its pages |
| MCP server | Yelp/yelp-mcp on GitHub (https://github.com/Yelp/yelp-mcp). It wraps the Yelp Fusion AI API with one yelp_agent tool and needs a Yelp Fusion AI key, not a Places API key. | No official server listed |
Where Openpath fits
If the agent needs a local business to message in Austin, Texas, Openpath returns the listings themselves, free and with no key. See Openpath vs Yelp Places API and Openpath vs Azure Maps Search.
Questions people ask
What do I need before I can use Yelp Places API?
A Yelp developer account (a business email is required for the trial) and a private API key. Paid plans need a credit card on file.
Is Yelp Places API free?
A 30-day trial with up to 5,000 API calls, for evaluation only, not commercial use. There is no permanent free tier.
What do I need before I can use Azure Maps Search?
An Azure subscription with an Azure Maps account. Authentication is by Shared Key, Microsoft Entra ID or SAS token.
Is Azure Maps Search free?
5,000 Search transactions a month.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
Yelp Places API, read on October 15, 2026:
- business.yelp.com/data/resources/pricing: “$229 per month plus $5.91 per additional 1,000 API calls”
- business.yelp.com/data/resources/pricing: “$299 per month plus $6.57 per additional 1,000 API calls”
- business.yelp.com/data/resources/pricing: “$643 per month plus $14.13 per additional 1,000 API calls”
- business.yelp.com/data/resources/pricing: “Receive 5,000 free API calls during the 30-day trial period”
- business.yelp.com/data/resources/pricing: “Start 30-day free trial Business email required”
- business.yelp.com/data/resources/pricing: “$25 / 1,000 API calls Minimum 1,000 daily API calls”
- docs.developer.yelp.com/docs/places-faq: “These API calls are STRICTLY FOR EVALUATION AND NOT FOR COMMERCIAL DEPLOYMENT”
- docs.developer.yelp.com/docs/places-faq: “This plan includes 30,000 API calls per month by default”
- docs.developer.yelp.com/docs/places-intro: “valuable information such as name, address, phone number, Yelp rating, price levels, and review counts”
- docs.developer.yelp.com/docs/places-intro: “The Yelp Places API uses private key authentication to authenticate all endpoints.”
- docs.developer.yelp.com/docs/places-intro: “millions of businesses around the world”
- terms.yelp.com/developers/api_terms: “opt into a paid subscription program by providing credit card and other necessary information”
- terms.yelp.com/developers/api_terms: “cache, record, pre-fetch, or otherwise store any portion of the Yelp Content for a period longer than twenty-four (24) hours”
- terms.yelp.com/developers/api_terms: “use it to update or create your own database of business listing information”
- terms.yelp.com/developers/api_terms: “Submit or ingest any Yelp Content into any Generative AI Model (e.g., prompts that contain any Yelp Content into ChatGPT”
- terms.yelp.com/developers/api_terms: “for the purpose of training, developing, enhancing, or fine-tuning any Generative AI Models without Yelp’s prior written approval”
- github.com/Yelp/yelp-mcp: “MCP server for exposing tools powered by Yelp's data”
- docs.developer.yelp.com/docs/resources-supported-locales: “Following are the locales Yelp Places API supports.”
Azure Maps Search, read on October 15, 2026:
- azure.microsoft.com/en-us/pricing/details/azure-maps: “Meters Free <500K 500K+ ... Search 5,000 $4.50 Contact Us”
- azure.microsoft.com/en-us/pricing/details/azure-maps: “Unless otherwise specified, the prices below are per 1,000 transactions.”
- learn.microsoft.com/en-us/azure/azure-maps/rest-api-azure-maps: “search for places and businesses by name or category”
- learn.microsoft.com/en-us/azure/azure-maps/migrate-search-v1-api: “Azure Maps Search API version 1.0 has been superseded by Search API version 2026‑01‑01”
- learn.microsoft.com/en-us/azure/azure-maps/migrate-search-v1-api: “While Search v1 continues to function, new development should use the latest Search API”
- learn.microsoft.com/en-us/rest/api/maps/search/get-search-poi: “Details of the returned POI including information such as the name, phone, url address, and classifications.”
- learn.microsoft.com/en-us/azure/azure-maps/azure-maps-authentication: “Azure Maps supports three authentication methods: Shared Key, Microsoft Entra ID, and Shared Access Signature (SAS) Token.”
- microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA: “Results may not be stored for longer than: (i) the validity period indicated in returned headers; or (ii) 6 months, whichever is shorter.”
- microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA: “Customer may not cache or store results delivered by the Azure Maps API for the purpose of scaling such Results”
- microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA: “Customer may not modify or create a derivative work based on any content using machine learning or artificial intelligence”
- microsoft.com/licensing/terms/productoffering/MicrosoftAzure/MCA: “Customer may not use Azure Maps or any part thereof to create a competing database or service”