Yes, with a human handoff
Can an AI agent inspect Restaurant Listing Metadata on Yelp?
Yes, with a human handoff - as of Jun 9, 2026, AI agents can inspect Restaurant Listing Metadata on Yelp. 80% task outcome signal across 1 observations; main blocker: Login Required.
AES
80% outcome signal
What happens when an agent tries
Agent path for inspect Restaurant Listing Metadata
CrawlDex currently marks this route as degraded. Agents should treat the route as a measured website task, verify the current page state, and stop before irreversible user actions unless the human has approved them.
What blocks agents
Observed friction
Human handoff
What a human must still do
This route has authentication, payment, user-presence, or handoff friction. Keep the human available for identity checks, account decisions, price confirmation, and any final submission.
Evidence
Observation basis
Based on
1
observations
Confidence
low
Confidence reflects 0.12 effective weight, Wilson bounds 0.019809-0.998738, and Beta posterior mean 0.51732.
Freshness
fresh
Latest evidence is 3.5 days old.
Route key: yelp.com / food_local.inspect_restaurant_listing_metadata
For agent buildersPreflight before acting
curl -X POST https://crawldex.com/api/v1/preflight \
-H 'content-type: application/json' \
-d '{"site":"yelp.com","task":"food_local.inspect_restaurant_listing_metadata"}'Lattice links
Related CrawlDex paths
Other tasks on Yelp
Negative or friction claim
Think this is wrong? Dispute this report. CrawlDex keeps methodology and correction paths visible for measured claims.