The agent successfully assembled a comprehensive overview of Azki by working around a Persian-language site with minimal English documentation and no dedicated About or Pricing pages. The homepage ([1]) was fetched but unintelligible without translation; direct navigation to standard info pages failed ([3], [4], [5]), forcing the agent to rely on web search ([7], [9]) and third-party aggregator sites ([10], [11]) to answer the core questions about what Azki does, who it's for, how it's priced, and how it differs from competitors. The site itself does not publish this information in an agent-accessible form.

• ›The primary azki.com domain returned only Persian-language HTML; no English version or machine-readable structured data (schema.org, meta descriptions) was present to expose positioning, pricing, or business model to an agent.
• ›Critical info pages (/about, /pricing, /en) returned 404s, indicating the site does not publish canonical reference documentation that would normally serve discovery and identity queries.
• ›The agent retrieved substantive answers from external sources (PitchBook [7], InsurTech List [11], Iran-focused tech news [10]) rather than from azki.com itself; these sources contained company profile, funding, market position, and service details that Azki's own site did not expose.
• ›The agent explicitly cited four external sources and zero content from azki.com in its final answer, revealing a complete reliance on prior knowledge and web search to answer a discovery-evaluation task about the company.
• ›The site is optimized for existing Iranian users on mobile (likely app-first strategy with the Bimito/Google Play presence [7, 9]) and does not publish outward-facing positioning or comparative content for new audiences or agents.