# The Moat The defensibility is not the discovery technique; it is the maintained shared graph that compounds with use. Any single route can be reverse-engineered by anyone. What is hard to copy is a graph of routes that stays fresh as thousands of sites change, because that requires continuous traffic, feedback, and maintenance rather than a one-time scrape. The Maintenance Network paper makes exactly this distinction: a static registry decays, while a graph kept current by real usage is a productive asset whose value is its freshness, not its size. The reason this compounds is that every reused route makes the next agent's task cheaper, and every agent's feedback makes the graph more trustworthy, so usage and quality reinforce each other. That loop is the routing-infrastructure upside layered on the wedge: as more agent traffic routes through the graph, the graph becomes the cheaper default, and the cheaper default attracts more traffic. The honest boundary for diligence: the wedge is shipped and measurable today; the fuller accountability and route-economy layer is research direction documented in the papers, not a claim of current revenue mechanics. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.unbrowse.ai/for-investors/the-moat.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.