What does maple.inc do and who is it for? Explain it back to me.
- web search75%
- prior knowledge25%
The agent successfully assembled a comprehensive explanation of Maple.inc by working around the site's Cloudflare protection—direct fetches of maple.inc returned 403 errors, forcing reliance on web search and third-party review sites. The agent retrieved core product details (voice AI for restaurant phone orders/reservations), pricing ($85–$220/month), target audience (SMB restaurants), and competitive positioning by synthesizing information from search results, third-party reviews, and blog posts. The site itself was not directly navigable for the agent, but sufficient information was surfaced through search engine indexing and external coverage to construct a coherent, well-sourced answer.
- ›Direct access to maple.inc failed completely (steps [1] and [6] returned Cloudflare challenges), forcing the agent to rely entirely on search-discovered third-party content and cached/indexed descriptions rather than the authoritative source.
- ›Search results and third-party review sites (perfectvenue.com, loman.ai) provided the bulk of product information—pricing tiers, core features (call answering, order taking, reservations), and competitive comparisons were extracted from external evaluations, not Maple's own documentation.
- ›The agent identified significant gaps it could not fill: payment processing during calls, concurrent call handling limits, exact upselling mechanics, mobile app capabilities, and third-party review availability. These gaps persist because the site's primary documentation was inaccessible and third-party coverage is sparse.
- ›The agent's final answer relied heavily on prior knowledge synthesis (25%) and web search (75%), with no ability to fetch primary pages. The competitive comparison table and many feature details appear to be inferred/synthesized rather than directly quoted from accessible sources.
- ›Site agent-readiness is low: Cloudflare protection blocks automated access entirely, pricing and product pages are not fetchable, and the agent cannot independently verify claims like the '92% resolution rate' against first-party documentation.
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 →