Travel Concierge CLI

**Judgement** A focused, high-utility scraping-based CLI that reliably attempts to surface direct contact details for accommodation listings across major booking platforms. Well-suited for automation and agent integration thanks to its simple interface and JSON output, but inherently constrained by scraping fragility and platform anti-bot/ToS limitations. **What it does well** - Extracts a **structured dossier** of contact methods (phone, email, WhatsApp, social links, website, maps URL) plus property/host info from a single listing URL. - Supports **multiple large platforms** (Airbnb, Booking.com, VRBO, Expedia) with a unified workflow. - Offers **JSON output** for scripting and OpenClaw-style agents, and verbose mode for debugging. - Optional **Google Places API** can significantly improve accuracy and trustworthiness of phone/website fields. **Key risks / limitations** - **Scraping fragility**: Any layout, markup, or anti-bot change on Airbnb/Booking/VRBO/Expedia can break or degrade results without warning. - **ToS & legal/compliance risk**: Automated scraping of commercial platforms may violate their terms of service or applicable laws in some jurisdictions; usage should be carefully reviewed by the operator. - **Platform restrictions & CAPTCHAs**: Some listings may require browser automation (agent-browser) or may be partially inaccessible, leading to incomplete data or failures. - **Ethical concerns**: Facilitating direct booking can bypass platform protections (dispute resolution, insurance), and contacting hosts outside platform channels may be discouraged by those services. **Recommended scenarios** - As a **backend utility** for agents that, when given a listing URL by the user, attempt to find direct contact methods and present them in a structured way. - For **power users or travel professionals** who understand scraping limitations and want to integrate direct-contact discovery into their tooling. - In workflows where **JSON output** is consumed by other systems (e.g., CRMs, trip planners) and occasional scraping failures are acceptable and handled gracefully. **Not ideal when** - Strong guarantees of **stability, completeness, or long-term reliability** are required. - The deployment context has **strict compliance requirements** around ToS adherence or scraping limitations. - Users expect **real-time, consistently accurate coverage** for every listing without understanding the inherent variability of web scraping.