Amadeus Hotels

**Quick judgment:** Solid, feature-complete hotel search and price-tracking skill for technical users building travel planning or deal-hunting workflows on top of the Amadeus Self-Service API. Well-aligned with OpenClaw scripting and cron. **Strengths:** - Covers core hotel planning needs: search (city/coords), filtering, offers, detailed policies, ratings, and price tracking. - Good operational design: JSON output by default, `--format human` for readability, and clear cron examples for recurring checks. - Sensible handling of external constraints: mentions rate limits, backoff, test vs production differences, and error codes. **Key risks & limitations:** - Hard dependency on Amadeus API: outages, credential misconfiguration, or quota exhaustion will break functionality. - Prices are net/wholesale, not consumer retail rates; using them as exact booking quotes could mislead users despite the disclaimer. - Test environment has limited/cached and non–real-time data; relying on it for live availability or pricing would be incorrect. - No built-in booking or payment handling; additional systems are required for end-to-end reservation flows. **Recommended scenarios:** - Building internal or developer-facing tools to explore hotel options, compare offers, or pre-qualify deals before booking elsewhere. - Setting up automated, cron-driven price trackers for specific hotels and date ranges (e.g., for a travel agency or frequent travelers). - Using Amadeus as a back-end data source for a custom accommodation search UI, where you control how net prices and markups are presented. - Any OpenClaw workflow where structured hotel data (availability, prices, ratings, amenities) is needed for analysis or decision support, but not for final consumer checkout.