doku.com
success
Claude Code
intent
What does doku.com do and who is it for? Explain it back to me.
11steps
52.9sduration
$0.4763cost
106,517tokens
15 steps4 reasoning steps2 searches
home
/en-us
docs
/en-us/payment-gateway
/layanan
/en-us/products
/en-us/about
/en-us/payout
/solusi
search
search
100%
on-site discovery
44%
reliability
56%
link following
path origin
- previous resource56%
- prior knowledge44%
insight
The agent assembled a comprehensive explanation of DOKU by combining fragments from the live website (homepage, pricing, about pages) with third-party research sources, since DOKU's own site had broken product pages and incomplete information architecture. The final answer covers what DOKU does, who it serves, pricing, and competitive positioning, but required heavy reliance on external sources and prior knowledge to fill gaps left by the site's limited accessible content.
- ›Step [1] and [2] (homepage in Indonesian and English) provided foundational positioning as 'payment technology company' and 'payment gateway pioneer in Indonesia,' but returned only metadata-level content in the fetches shown—the agent relied on prior knowledge to extract substantive details.
- ›Step [3] (pricing page) successfully returned pricing details but appeared truncated in the response; the agent extracted transaction fee structure (2.80% + IDR 2,000 for cards, 0.7% for QRIS, etc.) but had to infer that 'no hidden fees' was a site claim rather than seeing that content directly in the truncated HTML.
- ›Steps [5], [7], [8] (attempted product pages: /en-us/products, /en-us/payment-gateway, /en-us/payout) all returned 404s—critical content about DOKU's core offerings was inaccessible, forcing the agent to rely on external sources.
- ›Step [6] (about page) returned 200 but the response was truncated, limiting what could be extracted about the company's history, licensing, and scale.
- ›Steps [12] and [13] (web searches) became primary sources of truth. Search [12] returned titles linking to third-party comparison/review sites; search [13] returned a snippet linking to 'Complete Payment Gateway Solution for Businesses | DOKU' on doku.com itself, but the agent never fetched that URL—it only cited the external sources in the final bibliography.
- ›The agent's final response cites 7 external sources (software-listing.com, dodopayments.com, tracxn.com, etc.) but none of those URLs appear in the trajectory as fetched steps. This indicates the agent used search result snippets and prior knowledge to construct the competitive analysis and detailed feature list, rather than extracting them from doku.com directly.
- ›The site is built on Webflow (noted in meta tags) and appears to be a recent redesign with incomplete navigation—the agent attempted logical URL patterns (/products, /payment-gateway, /payout, /layanan, /solusi) but the site structure does not expose these sections, leaving core product descriptions unfetchable.
Help the next agent finish on doku.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 →