ora
auno.vn
success
Claude Code
intent

What does auno.vn do and who is it for? Explain it back to me.

23steps
133.4sduration
$1.5463cost
407,943tokens
31 steps8 reasoning steps8 searches
home
/vi
/wp-json/wp/v2/pages
/wp-json/wp/v2/pages
docs
/wp-json/wp/v2/posts
/wp-json/wp/v2/pages/2
search
/about-us
/amanaki-boutique-saigon
search
/wp-json/wp/v2/pages/2
search
search
search
home
search
search
search
/en/amina-boutique-hotel
/contact
sitemap
/page-sitemap.xml
87%
on-site discovery
80%
reliability
60%
link following
path origin
  • previous resource60%
  • web search13%
  • prior knowledge27%
insight

The agent successfully assembled a comprehensive explanation of Amanaki Group by combining fragments from the official auno.vn site (which rendered minimally in machine-readable form) with external sources discovered via web search, particularly amanaki.vn and ANIMA's dedicated sites. The auno.vn domain itself proved difficult to navigate programmatically—the WordPress REST API endpoints returned truncated HTML payloads that didn't surface the full property descriptions, pricing, or positioning—forcing the agent to rely heavily on web search and sister domains to answer the task.

  • ›Steps [18] and [19] fetched amanaki.vn (a sister domain), which returned structured schema.org markup and readable descriptions of properties, positioning, and values—this was the primary content source for 'what they do' and 'who it's for.' The auno.vn domain itself returned only truncated HTML, suggesting the site's publishing model prioritizes visual presentation over machine-readability.
  • ›Web searches [16], [24], [27], [28] yielded snippets and links that populated pricing tiers, property names (Amina, ANIMA, OMM, ÚNU), and competitive differentiation. The agent did not find pricing or detailed property listings directly on auno.vn; it had to infer them from external booking sites and related articles.
  • ›The agent correctly identified structural confusion on auno.vn itself—branding inconsistencies between 'Amina,' 'Amanaki,' and 'ANIMA' are real. The site publishes a portfolio presentation but delegates booking and detailed information to external platforms (Booking.com, Agoda, amanaki.vn). This is a discovery-layer friction point: the site does not surface its own value proposition clearly enough for machine consumption.
  • ›Steps [11] and [13] (sitemap.xml) and [4], [5], [12], [14], [21] (WordPress REST API) demonstrated that auno.vn is a WordPress site with accessible APIs, but the responses were truncated or contained minimal structured content, indicating either rendering complexity or deliberate content gating. The site does not publish its core business model, property details, or pricing in a queryable, machine-readable format.

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 →