The agent could not directly access omio.com (all direct fetches returned 403 Cloudflare blocks), but successfully assembled a comprehensive answer by synthesizing web search results and prior knowledge about the platform. The site itself is not machine-readable to agents; the agent had to rely entirely on search engine indexing and third-party review sites to understand Omio's value proposition, pricing model, and competitive positioning.

• ›Step [3] (web search for 'omio.com what is it travel booking') returned snippet titles that established Omio as a multi-modal aggregator; steps [10], [11], [12] provided comparative analysis, pricing details, and review-based differentiation that formed the core of the final answer.
• ›The site publishes information via search indexing (titles, snippets) rather than machine-readable structured data, FAQ pages, or API documentation. The agent never accessed a live page from omio.com itself—all content came from search engine snippets, app store metadata, and third-party review sites.
• ›Omio's Cloudflare protection blocks all direct agent access, forcing reliance on search engines as the sole discovery layer. This severely degrades agent-readiness: the agent cannot verify current pricing, confirm feature descriptions, or access primary documentation. The Help Center articles (steps [7], [10]) were also blocked, leaving the agent unable to retrieve authoritative fee documentation.
• ›The agent successfully inferred pricing ambiguity (variable service fees, lack of upfront transparency) from review articles and Help Center article titles, rather than from reading the actual fee documentation—this is a workaround, not a direct discovery.
• ›Multi-leg journey construction and competitive differentiation (vs. Trainline, Skyscanner, Rail Europe) came from third-party comparison articles, not from Omio's own positioning. The agent synthesized these rather than reading Omio's own messaging.