doana.ca
partial
Claude Code
intent

What does doana.ca do and who is it for? Explain it back to me.

22steps
129.9sduration
$1.8156cost
261,187tokens
36 steps14 reasoning steps15 searches
home
/en
/en/about
/en/features
search
search
search
search
/en/pricing
/en/blog
search
search
search
search
/en/demo
search
search
search
search
search
search
search
100%
on-site discovery
100%
reliability
43%
link following
path origin
  • previous resource43%
  • prior knowledge57%
insight

The agent partially assembled an understanding of Doana through web search results and prior knowledge, since the website itself is client-side rendered and returned no human-readable content. The agent inferred that Doana is an AI-powered customs automation platform specializing in aviation document extraction (EASA Form 1, invoices, air waybills), but could not retrieve specific pricing details, feature depth, or competitive differentiation from the site itself—those details either don't exist in public form or are behind login/contact walls. The site proved almost entirely opaque to the agent's direct navigation.

  • ›All direct fetches to doana.ca (steps [1], [3], [5], [6], [7], [15], [23]) returned identical Next.js boilerplate HTML with no readable content—client-side rendering made the site invisible to the agent without a browser runtime.
  • ›The agent reconstructed its understanding almost entirely from web search snippets (steps [9], [11], [14], [29], [32]) and prior knowledge (57% of fetches sourced this way), not from the site itself. Search result titles and metadata provided the core facts: 'AI Customs Agent for Aviation, MRO & Freight' and references to EASA Form 1, customs automation, and aviation/MRO targeting.
  • ›The site explicitly published almost no structured information about pricing, features, competitors, or team. The agent noted this directly: 'I could not find specific pricing tiers, per-document costs, or pricing examples' and 'I found no published case studies, customer testimonials, or performance metrics.' This absence forced reliance on inference and external search.
  • ›The site's glossary page (doana.ca/glossary, mentioned in step [14]) was identified but not fully examined—it appears to be an island of static content in an otherwise client-side app, suggesting uneven information architecture.
  • ›The agent successfully identified Doana's specialization and use case (aviation customs, email-to-data extraction, regulatory compliance) through accumulated search context, but could not verify feature claims or pricing models directly from doana.ca itself.

Help the next agent finish on doana.ca

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 →