The agent assembled a partial understanding of Unloc by combining fetches from the developer documentation site, the main Unloc website, and web search results. It successfully identified what Unloc does (digital mobile key platform), who it serves (property managers, developers, residents), and competitive positioning, but failed to extract clear pricing information—a core part of the task. The main Unloc site (unloc.app) surfaced limited machine-readable content; developer.unloc.app provided technical API docs but no pricing or business model details, forcing the agent to acknowledge gaps rather than answer them.

• ›Steps [1], [3], [8], [9] fetched from developer.unloc.app and returned HTML from a ReadMe-hosted documentation site; the responses were truncated and did not contain pricing, tiers, or cost models. The agent noted 'API Documentation vs. Business Model Disconnect' — technical docs were present but business terms were absent.
• ›Steps [5], [6], [13], [16], [18] fetched from unloc.app (the main marketing site) and returned HTML from Webflow; these also appeared to be server-side rendered or client-heavy pages that did not yield extracted pricing text in the trajectory. The agent could not extract clear pricing despite multiple attempts at /pricing endpoints.
• ›The agent relied heavily on web search (steps [4], [7], [10], [11], [14], [17], [19], [20], [21], [22]) to discover pages and infer use cases and competitors, but search results only returned link titles and metadata—not pricing details. The agent had to construct the answer by combining fragments from search result titles, prior knowledge of the digital key market, and the limited technical content it could retrieve.
• ›The agent explicitly called out three major gaps: (1) no public API pricing or free tier information, (2) no cost-per-key or per-lock models disclosed, (3) 'Contact Sales' redirects instead of transparent pricing. This indicates the site deliberately obscures pricing from public view, making agent extraction impossible without executing a contact form or speaking to sales.
• ›The agent's final response cites [developer.unloc.app/docs] and [unloc.app/en] URLs as sources, but none of these fetches yielded the pricing section the user requested. The agent was honest about this limitation: 'This is where things get fuzzy' and 'I couldn't extract clear, detailed pricing information.'