The agent successfully assembled a comprehensive explanation of RNO1's services, target market, pricing model, and differentiation by combining data from the main RNO1 website (rno1.global) and the Appear Protocol metadata files. The appear.rno1.com subdomain itself is not a separate product but rather an AI-optimized metadata layer; the agent correctly identified this by fetching the .well-known protocol files. The site's main domain was difficult to extract complete information from (truncated HTML responses), forcing the agent to rely on alternative domains and protocol files rather than a single authoritative source.

• ›Steps [10], [11], [12] returned actual service offerings, positioning language ('Radical Digital Experiences™'), and client targeting information from rno1.global, which appears to be the primary public-facing domain. The appear.rno1.com homepage fetch [1] returned only truncated HTML and did not surface actionable content.
• ›Steps [17] and [18] returned machine-readable JSON from the Appear Protocol standard (.well-known/appear.json and .well-known/appear-index.json), which revealed that appear.rno1.com is a protocol-compliant subdomain serving the same RNO1 entity (domain: www.rno1.com), not a separate service. The agent correctly demystified this by fetching and interpreting the protocol files.
• ›Pricing information was not explicitly published on any fetched page; the agent relied on web search results (steps [7], [8]) and prior knowledge to reconstruct typical project and subscription pricing. The site does not host a public pricing page, making this information agent-hostile and requiring external sources to validate.
• ›Service details, target audience segments (venture-backed startups, Web3, D2C), and subscription product names (Revolve, Retrn, Ryde) were extracted from the rno1.global domain rather than appear.rno1.com, indicating that the main domain is the authoritative source for business information.
• ›The agent's final answer was well-structured and complete, but the site itself required workarounds: truncated HTML from the primary domain, reliance on a secondary domain (rno1.global), protocol file inspection, and web search augmentation to deliver a coherent picture. This indicates moderate agent-friendliness with friction in discovery.