didit.me
success
Claude Code
intent
What does didit.me do and who is it for? Explain it back to me.
12steps
65.4sduration
$0.1817cost
197,789tokens
13 steps1 reasoning step4 searches
home
docs
search
/industries/identity-v…
docs.home
docs
search
docs
docs
docs
search
search
50%
on-site discovery
100%
reliability
38%
link following
path origin
- previous resource38%
- web search50%
- prior knowledge13%
insight
The agent successfully assembled a comprehensive explanation of didit.me by combining homepage/pricing pages with strategically targeted blog posts and comparisons. The site made discovery easy through self-authored comparison articles and pricing transparency, but required web search to surface core positioning and competitor differentiation rather than having this structured clearly on the main product pages.
- ›Step [0] (homepage) and step [1] (pricing page) provided the foundation—clear per-check pricing ($0.33 for full KYC) and free monthly allowance were directly stated, making pricing the least confusing element.
- ›Steps [6] and [7] were critical: the agent found didit.me's own Onfido vs Jumio vs Didit blog post via web search, which explicitly positioned their differentiation (cost, modularity, speed). This self-authored comparison was more useful than navigating product pages.
- ›The agent had to infer 'fraud detection specifics' were absent from readily accessible pages—it noted this as a gap. The fintech industry page ([3]) returned content but loaded empty, suggesting rendering or content structure issues that forced reliance on blog articles instead.
- ›Pricing and 'who it's for' were surfaced natively (pricing page, homepage, industry pages), but 'how it's different' required the agent to fetch and read didit.me's own comparison blog to avoid guessing. The site did not package this on a dedicated alternatives/competitors page.
- ›The agent relied on prior knowledge (13%) and web search (50%) partly because core narrative and positioning details were distributed across blog content rather than consolidated in product-facing pages; developer-friendly documentation existed ([4] docs.didit.me) but was not a primary source for business-level understanding.
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 →