Try the Nearby DoorDash stores API

- Results are always ordered nearest first, and each row carries `distance_meters` from the query point. There is no `sort` parameter, because distance ordering is the only meaningful order for a radius query. - Only stores with coordinates can match a radius query, so every row here has `latitude` and `longitude`; `address` and `phone` are populated whenever DoorDash's store card provides them. - `display_status`, `display_asap_time`, `asap_available`, and `pickup_available` are a **point-in-time pickup observation** from the crawl, not a live ordering capability. - Coverage is not provably exhaustive: the census tiles the market in fixed cells and stops at a maximum depth, so a very sparse area can return fewer stores than a live Explore query would, and an exhausted tile is reported as `terminal` rather than silently re-crawled forever. - A not-yet-populated dataset, or a coordinate with no stores in range, returns an empty result (`total: 0`), not an error.