tubahealth.com
success
Claude Code
intent

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

14steps
76.8sduration
$0.9874cost
125,848tokens
18 steps4 reasoning steps8 searches
home
/en
search
/en/pricing
/en/about
search
search
/en/questions
search
search
/en/questions
search
search
search
83%
on-site discovery
67%
reliability
33%
link following
path origin
  • previous resource33%
  • web search17%
  • prior knowledge50%
insight

The agent successfully assembled a comprehensive explanation of Tuba Health by combining sparse site content with external sources, particularly news articles and funding announcements. The website itself proved minimally informative—direct fetches returned structurally incomplete HTML without extractable content—so the agent relied heavily on web search results and prior knowledge to answer all four dimensions of the task (what, who, pricing, differentiation). The site's lack of public pricing, competitive positioning, or detailed feature documentation meant the agent had to work around the core knowledge gaps rather than retrieve them directly.

  • ›Direct site fetches (steps [1], [2], [6], [12]) returned HTML with no usable content visible in the responses—truncated at 4400 characters with no meaningful text. The site appears to be a Next.js app that renders content client-side, making static HTML fetches non-informative.
  • ›Web search results (steps [4], [11], [14]) were the only sources that returned substantive information: announcement articles from ArabFounders, Wamda, and Arageek provided details on founders, funding ($8M pre-seed), target market (employers in Saudi Arabia), and the AI-first positioning. These articles were cited in the final response.
  • ›The site does not publicly disclose pricing, implementation timelines, revenue model, or competitive differentiation—forcing the agent to flag these as 'confusing or missing' rather than answer them. The /pricing route returned a 404, confirming no dedicated pricing page exists.
  • ›The agent's answer was constructed 50% from prior knowledge (company positioning, market context), 33% from previous artifacts (likely context about Tuba from earlier runs), and only 17% from live web search. This distribution reflects heavy reliance on external context because the site itself does not surface these answers.
  • ›The site's language auto-redirect (Arabic at [0], English at [2]) and dual-app strategy (My Tuba + Tuba Business apps) are evidence of localization, but the website's content remains inaccessible to automated analysis.

Help the next agent finish on tubahealth.com

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 →