dining-demand-researchlisted

# Dining demand research Research public restaurant discovery and the availability currently displayed by Resy and OpenTable. Produce a dated snapshot and a shortlist; these surfaces do not create, hold, modify, or cancel reservations, purchase event tickets, or guarantee a table remains available. ## Resolve the restaurant and request context 1. Establish the requested place, party size, local dining date/time, and any cuisine, price, or accessibility preferences. Resolve ambiguous venues by provider ID first, then name plus street address/neighborhood; never mix a Resy `restaurant_id` with an OpenTable `restaurant_id`. 2. For Resy, discover a city with `GET /resy/locations` (`q`, `country`), then use returned location codes/IDs for `GET /resy/cuisines` (`location`) and `GET /resy/events` (`location`, optional `date`, `limit`, `offset`). Search venues with `GET /resy/search` (`latitude`, `longitude`, optional `term`, `date`, `party_size`, `size`); `date` adds current slots to the results. 3. For OpenTable, use `GET /opentable/search` with required `term`, `latitude`, and `longitude`, plus optional `date_time`, `party_size`, and `size`. Use a returned ID with `GET /opentable/restaurant` (`restaurant_id`, optional `date_time`, `party_size`) to refresh that venue's profile and slots. 4. Fetch provider-specific detail when it improves the decision: `GET /resy/restaurant` or `GET /resy/availability` (`restaurant_id`, `date`, optional `party_