ora
dehradunairportcabservice.com
success
Claude Code · Haiku 4.51:01
intent

What does dehradunairportcabservice.com do and who is it for? Explain it back to me.

11steps
61.5sduration
$0.5937cost
83,143tokens
18 steps7 reasoning steps3 searches
home
home
docs
search
/airport
/car-rental/jolly-gran…
search
search
docs
/services
/contact
75%
on-site discovery
50%
reliability
25%
link following
path origin
  • previous resource25%
  • web search25%
  • prior knowledge50%
insight

The agent successfully assembled a comprehensive overview of Dehradun Airport Cab Service by combining fragments from the homepage, an About page, a specific route pricing page, and web search results. The site itself is partially navigable—pricing examples were discoverable via search results and a targeted route page, but core information like full service descriptions, contact details, and a complete pricing table were either fragmented across multiple pages or inaccessible (contact page returned a database error). The agent had to stitch together information from multiple sources and rely on search engine snippets rather than finding a single authoritative resource.

  • Steps [1] and [3] (homepage fetches) returned truncated HTML that did not fully expose the site's value proposition; the agent could not see the complete featured messaging despite two fetch attempts.
  • Step [7] (About page) and Step [13] (Jolly Grant route-specific page) provided concrete details: vehicle types, starting prices (₹999 for Sedan to Dehradun), and service features (verified drivers, fixed fares, 24/7 availability). These were the primary content-bearing sources for pricing and differentiation.
  • Steps [10], [15], and [16] (web search results) surfaced pricing examples and route-specific pages that the agent could not discover by guessing typical URL patterns—the site does not publish a centralized /pricing or /services page. Search results were essential to finding content.
  • Step [9] (contact page) returned a database error (HTTP 500), blocking access to customer service details; Step [5] and [6] (guessed /pricing and /services URLs) returned 404s, indicating the site does not organize information via standard service-discovery paths.
  • The agent was forced to assemble answers from fragments: pricing from route-specific pages, service overview from About + homepage meta description, and differentiators inferred from scattered claims about 'transparent pricing' and '24/7 availability' rather than a dedicated competitive positioning page.
  • The site lacks structured, agent-ready artifacts like schema.org markup for pricing, service categories, or business details; the agent reconstructed the narrative from HTML snippets, search indexing, and prior knowledge about the cab service market rather than consuming a machine-readable source.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →