ora
my-doctor.io
success
Claude Code · Haiku 4.51:37
intent

What does my-doctor.io do and who is it for? Explain it back to me.

20steps
97.1sduration
$0.2661cost
333,514tokens
33 steps13 reasoning steps7 searches
home
/en
docs
docs
sitemap
sitemap
/company
sitemap
sitemap
/telemedicine/%ed%83%8…
search
search
mydoctor-notice-d.home
search
/medical-cost-hub/hair…
/medical-cost/%ed%83%8…
search
search
search
search
92%
on-site discovery
77%
reliability
85%
link following
path origin
  • previous resource85%
  • web search8%
  • prior knowledge8%
insight

The agent gathered a reasonably complete picture of my-doctor.io's core function, target market, and competitive positioning, though key details—especially pricing—remained opaque. The site is Korean-only with no English version, and critical operational information like consultation fees are not published on public-facing pages. The agent had to assemble its answer from fragmented content (metadata, telemedicine page titles, medical cost comparisons), prior knowledge of the Korean telehealth market, and external sources (news articles, app store listings, wiki).

  • Step [1] (homepage) returned only Korean-language metadata and truncated HTML; no structured information about pricing, business model, or service details was surface-level. The agent could infer 'telemedicine app' from the title tag but nothing quantitative.
  • Steps [15] and [25] (telemedicine and medical cost pages) revealed the product's actual features—booking consultations and comparing medication prices across providers—but only through URL patterns and page titles; the HTML responses were truncated and offered no pricing data.
  • Step [12] (company page) was similarly content-sparse, containing only Korean metadata. The agent had to resort to external searches to find revenue figures, funding info, and competitive context.
  • Steps [27] and [18] (web searches) were the only sources that returned substantive, machine-readable answers: they surfaced news about Series A funding, 6x revenue growth, and user counts. These searches were necessary because the public website does not publish this information.
  • The site's medical cost hub structure (sitemaps, geographic URL hierarchy) suggests a working price-comparison engine, but individual pages were fetched truncated, preventing visibility into actual pricing logic or data.
  • Consultation fee structure and the exact mechanics of the telemedicine booking flow were never found—neither on the website nor in search results. The agent acknowledged this gap explicitly in its final response.
  • The site is entirely closed to non-Korean speakers and non-Korea-based users by design (no English version, Korea-specific regulatory context, app-only access to most features). A non-Korean agent would struggle significantly more.

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 →