Yelp
Yelp connects people with great local businesses. The Yelp Fusion API gives developers programmatic access to Yelp's database of millions of local businesses, ratings, reviews, photos, events, and category taxonomy, plus the Yelp Fusion AI conversational search endpoint. Core public capabilities include business search and discovery, business details, review excerpts, autocomplete, phone and address matching, and local event search. Partner-tier APIs add reviews response, leads, advertising, reservations, waitlist, checkout, and reporting. Authentication uses a Yelp API key passed as a bearer token.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Yelp the way a machine reads it — 75 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Yelp scores 73.8/100 (exemplar), with a separate agent-readiness read of 56/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Yelp
Each block below is one kind of artifact we hold for Yelp. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Yelp AI API
Conversational Yelp Fusion AI search and chat
Yelp Businesses API
Search, match, and retrieve local business data
Yelp Categories API
Yelp business category taxonomy
Yelp Events API
Local event search and details
Yelp Reviews API
Business review excerpts and ratings
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Yelp Fusion API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Yelp GraphQL API
Yelp exposes a GraphQL endpoint alongside its REST Fusion API, available at `https://api.yelp.com/v3/graphql`. The same bearer-token authentication used for the REST API applies...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Yelp Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Yelp Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Yelp Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Business Search
Search up to 240 businesses by location, term, category, price, and attributes.
Business Details
Retrieve rich detail for a business by id or alias, including hours, photos, and attributes.
Reviews
Retrieve review excerpts, ratings, and reviewer details for a business.
Autocomplete
Return search-term, business, and category suggestions as the user types.
Phone and Address Match
Resolve a phone number or postal address to Yelp businesses.
Events
Search and retrieve local events with timing, location, cost, and ticketing.
Category Taxonomy
Access the full Yelp business category list and per-category details.
Fusion AI
Natural language, multi-turn conversational search and business questions.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Yelp Fusion Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Yelp API Rules
SPECTRALYelp API Rules
SPECTRALJSON Schema 14
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AiChatRequest
JSON SCHEMAAiChatResponse
JSON SCHEMAAutocompleteResponse
JSON SCHEMABusinessDetail
JSON SCHEMABusinessHours
JSON SCHEMABusiness
JSON SCHEMABusinessSearchResponse
JSON SCHEMACategory
JSON SCHEMACoordinates
JSON SCHEMAEvent
JSON SCHEMAEventSearchResponse
JSON SCHEMALocation
JSON SCHEMAReview
JSON SCHEMAReviewsResponse
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 14
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Yelp Ai Chat Request Structure
JSON STRUCTUREYelp Ai Chat Response Structure
JSON STRUCTUREYelp Autocomplete Response Structure
JSON STRUCTUREYelp Business Detail Structure
JSON STRUCTUREYelp Business Hours Structure
JSON STRUCTUREYelp Business Search Response Structure
JSON STRUCTUREYelp Business Structure
JSON STRUCTUREYelp Category Structure
JSON STRUCTUREYelp Coordinates Structure
JSON STRUCTUREYelp Event Search Response Structure
JSON STRUCTUREYelp Event Structure
JSON STRUCTUREYelp Location Structure
JSON STRUCTUREYelp Review Structure
JSON STRUCTUREYelp Reviews Response Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 14
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Yelp Ai Chat Request Example
EXAMPLEYelp Business Detail Example
EXAMPLEYelp Business Example
EXAMPLEYelp Business Hours Example
EXAMPLEYelp Category Example
EXAMPLEYelp Coordinates Example
EXAMPLEYelp Event Example
EXAMPLEYelp Location Example
EXAMPLEYelp Review Example
EXAMPLEScroll within the panel for all 14 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Restaurant Discovery
Power restaurant and food discovery experiences with search, ratings, and photos.
Location-Aware Recommendations
Surface nearby, open, and highly-rated businesses based on user coordinates.
Reputation Monitoring
Track ratings and review excerpts for a portfolio of businesses.
Conversational Concierge
Build AI agents that answer natural language questions about local businesses.
Local Events Listings
Embed curated local event listings into apps and sites.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Zapier
Yelp Leads and Conversions APIs offer Zapier integrations for no-code workflows.
Model Context Protocol
Official Yelp MCP server exposes Fusion AI as an agent tool over MCP.
Webhooks
Reviews and Leads webhooks push real-time events to partner endpoints.
Resources
Every other property we hold for Yelp — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/yelp · machine-readable index on apis.io