The agent successfully assembled a comprehensive overview of Pitly by combining information from the live homepage (pitly.net, which pitly.fr redirects to) with external comparison articles. However, the site itself does not expose pricing, feature lists, or differentiation clearly—the agent had to infer most of this from competitor review sites and prior knowledge, then backfill with educated guesses about Pitly's positioning. The site is poorly navigable for this task: direct attempts to fetch /pricing, /features, /about all returned 404s, and the homepage HTML was not parsed to extract structured content.

• ›Step [9] (pitly.net homepage) returned raw HTML that the agent could not extract actionable information from—the response was truncated and appeared to be client-side rendered Next.js code. This single page is Pitly's primary asset but failed to deliver machine-readable content about what the product does, who it's for, or how it's priced.
• ›Step [16] (external car maintenance app comparison article) was actually the most content-bearing source—it included Pitly in a ranked list of alternatives, providing comparative positioning against MyAutoLog, CARFAX, Drivvo, and others. This external source told the agent more about Pitly's market position than Pitly's own site did.
• ›The agent attempted 7 direct fetch guesses at standard marketing page paths (/pricing, /features, /about, /fr/tarifs, /fr/fonctionnalites) before pivoting to web search. All returned 404s, indicating the site does not publish these standard entry points. The site relies entirely on the homepage to convey its value proposition.
• ›The agent never successfully parsed or extracted text from the pitly.net homepage itself—all the homepage fetches show truncated 'This is Next.js code' responses. The agent filled gaps by inferring from search results and citing external sources rather than the primary site.
• ›Pricing information was explicitly incomplete on-site: the agent correctly noted that Pitly is in free private beta with an invite-only model, but this detail likely came from the homepage CTA or Terms page, not from a dedicated pricing resource. No information about future pricing tiers, feature lockout, or multi-vehicle costs was available.