tempus.com
success
Claude Code
intent
What does tempus.com do and who is it for? Explain it back to me.
12steps
76.3sduration
$1.0826cost
89,136tokens
17 steps5 reasoning steps9 searches
home
search
/about-us
/faqs
search
search
search
search
search
search
search
search
33%
on-site discovery
0%
reliability
0%
link following
path origin
- web search67%
- prior knowledge33%
insight
The agent assembled a comprehensive explanation of Tempus.com entirely through web search and prior knowledge, because the primary website was blocked by a security checkpoint. Despite this access barrier, the agent successfully answered all four dimensions of the task (what they do, who it's for, pricing, differentiation) by synthesizing information from search results, third-party analyses, and news sources. The website itself proved to be agent-hostile; the agent had to work around it entirely.
- ›Direct fetches to tempus.com returned 429 security checkpoints (steps [1], [4], [5]), forcing the agent to rely entirely on web search and prior knowledge rather than the authoritative source.
- ›Web searches (steps [3], [7], [8], [9], [11], [12], [13], [14], [15]) returned news articles, third-party analyses, and company profiles that contained the information needed—suggesting the narrative is publicly available elsewhere but not directly from Tempus's own site.
- ›Pricing information came from third-party sources (step [7] via xpay.sh, step [15] via billing FAQs search result), not from a transparent pricing page on the site itself. Enterprise pricing for the Lens platform remains opaque—the agent correctly flagged this as a gap.
- ›The agent synthesized business model insight (flywheel between diagnostics and data/AI, margin breakdown, competitor differentiation) from financial analyses and company profiles (steps [11], [14]), not from product marketing.
- ›All 11 citations in the final response are either external sources (Wikipedia, Yahoo Finance, Uber Executives, etc.) or Tempus URLs discovered via search—none were fetched directly by the agent due to the security checkpoint blocking them.
- ›The site publishes FAQ and resource pages (flagged in step [9] and [15] search results) that likely contain patient cost and billing details, but these were inaccessible to the agent; the agent instead noted what it could not verify.
- ›The agent correctly identified regulatory/transparency gaps (FDA approval status of tests, patient out-of-pocket burden distribution) that it could not resolve from available sources.
See every agent that visits tempus.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 →