alleypin.co.jp
success
Claude Code
intent

What does alleypin.co.jp do and who is it for? Explain it back to me.

18steps
89.4sduration
$1.1087cost
198,810tokens
20 steps2 reasoning steps8 searches
home
/jp/pricing
/jp/service
/jp/features
/jp
/jp/contact
search
/jp/about
/jp/1talk-clinic-onlin…
search
docs
search
search
search
/en/1talk-crm
search
search
search
60%
on-site discovery
70%
reliability
40%
link following
path origin
  • previous resource40%
  • web search40%
  • prior knowledge20%
insight

The agent assembled a reasonably complete picture of AlleyPin's business through a mix of web search results and fetched pages, but had to work around significant site friction. The Japanese-language homepage and feature pages returned only partial information due to client-side rendering; the agent relied heavily on web search to discover that 1.Talk is the core product, then filled gaps using the English version of the site and a Taiwan-based pricing page. Pricing information remains opaque—the agent correctly identified that no transparent pricing is published, requiring contact for quotes.

  • ›Web search steps [7, 8, 12] were critical discovery vectors: they surfaced the product name (1.Talk), the company structure, and pointers to localized product pages that the homepage did not clearly expose. Without search, the agent would have struggled to understand the service hierarchy.
  • ›The Japanese homepage (steps [0, 5]) and features page [4] returned React/Next.js bundles with minimal server-side HTML content, making it nearly impossible for the agent to extract feature details or positioning without JavaScript execution. This forced reliance on search results and external pages.
  • ›Step [13] (Taiwan pricing page at alleypin.com/pricing) became a workaround source; it provided the only detailed pricing model the agent found, even though it was geographically misaligned with the task domain (alleypin.co.jp). The Japanese site offers no equivalent.
  • ›Steps [9] (About page), [10] (1.Talk appointment feature page), and [15] (English 1.Talk CRM page) were cited sources but returned heavily JavaScript-dependent pages; their value came from being cited as references rather than from extractable content. The agent appears to have inferred their content from context or prior knowledge.
  • ›The site published no differentiation vs. competitors, no transparent pricing, and no clear product hierarchy—all core task requirements. The agent had to synthesize these from search snippets, Crunchbase, and external press releases rather than from the site itself.

Help the next agent finish on alleypin.co.jp

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →