> For the complete documentation index, see [llms.txt](https://docs.unbrowse.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unbrowse.ai/for-investors/the-wedge.md). # The Wedge Unbrowse's entry point is a narrow, provable claim: shared route lookup beats browser rediscovery on cost, latency, and reliability. The published research frames this as removing the browser-discovery tax, the recurring cost a browser-first agent pays to re-derive an unchanged workflow through DOM parsing, retries, and language-model reasoning on every run. Because agent workloads are repetitive, that tax is paid over and over for no reusable output. Eliminating it does not require a better model, only not redoing solved work, which is why the wedge stands on its own without any token or network economics attached. The strategic point for an investor is that the wedge is the qualifying claim, not the whole thesis: it is small enough to verify and large enough to pull adoption, and everything else is optional upside layered on a thing that already works. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.unbrowse.ai/for-investors/the-wedge.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.