What problem does it solve?
Travel search tools fail constantly: APIs hit rate limits, MCP servers return errors, scraping gets blocked, and IP allowlists reject first-time calls. Without a fallback plan, a single failure stalls the entire flight or hotel search workflow.
Core Features & Use Cases
- Tool-by-Tool Fallback Table: Maps every primary tool (Duffel, Ignav, Skiplagged, Kiwi, Seats.aero, Trivago, LiteAPI, and more) to its best fallback so one failure never blocks a search.
- IP Allowlist Diagnostics: Recognizes error signatures like AwardWallet's IP_DENIED and TripAdvisor's explicit deny, then walks through whitelisting the user's current IP.
- Failure-Mode Guidance: Covers Patchright browser issues (bot detection, 2FA loops, login form changes), Docker pull failures, and misleading "no cached availability" results from Seats.aero.
- Use Case: Skiplagged returns a 502 during a flight search. Instead of giving up, consult the fallback table, switch to the Kiwi.com MCP, and tell the user which source was used.
Quick Start
When a travel search tool fails or returns an error, consult this fallback guide to pick the next-best source and continue the search.