# Internal APIs Are All You Need Implementation-aware companion docs for the Unbrowse whitepaper. * Authors: Lewis Tham, Nicholas Mac Gregor Garcia, Jungpil Hahn * Canonical PDF: [unbrowse-whitepaper.pdf](https://github.com/unbrowse-ai/unbrowse/blob/stable/docs/whitepaper/unbrowse-whitepaper.pdf) * Status: official paper plus implementation-aware companion docs * Canonical paper draft synced here: April 1, 2026 > Important The PDF mixes shipped product behavior, research results, and forward-looking economic design. These companion docs separate those three things so readers can tell what exists in the codebase today, what already ships in the current x402/payment lane, and what is still coming soon. ## What This Companion Covers * What Unbrowse ships today * Which whitepaper claims map directly to the codebase * Which paper sections are partial implementations * Which paper sections are still `coming soon` beyond the shipped payment lane * Which evaluation paths are current product truth versus paper benchmark context ## The Short Hook The web contains a huge amount of usable value, but most of it is trapped behind interfaces built for humans. Unbrowse is a way to unlock that layer for agents. It learns the request paths underneath websites, turns successful routes into reusable skills, and makes later agents faster and less brittle because they do not have to rediscover the same workflows from scratch. ## Quick Navigation * [Unbrowse In Plain English](https://docs.unbrowse.ai/start-here/plain-english) * [For Technical Readers](https://docs.unbrowse.ai/by-audience/for-technical-readers) * [For Investors](https://docs.unbrowse.ai/by-audience/for-investors) * [Marketplace and Maintenance](https://docs.unbrowse.ai/reference/network-layer) * [What Is Unbrowse?](https://docs.unbrowse.ai/start-here/what-is-unbrowse) * [The Problem](https://docs.unbrowse.ai/start-here/the-problem) * [Mental Models](https://docs.unbrowse.ai/start-here/mental-models) * [How It Works](https://docs.unbrowse.ai/start-here/how-it-works) * [Key Concepts](https://docs.unbrowse.ai/reference/key-concepts) * [System Today](https://docs.unbrowse.ai/reference/system-today) * [Paper vs Product Status](https://docs.unbrowse.ai/reference/paper-vs-product) * [Evaluation and Benchmarks](https://docs.unbrowse.ai/reference/evaluation) * [Coming Soon](https://docs.unbrowse.ai/reference/coming-soon) ## Recommended Reading Order Start with [For Investors](https://docs.unbrowse.ai/by-audience/for-investors) or [For Technical Readers](https://docs.unbrowse.ai/by-audience/for-technical-readers) for the public/product truth. Read [Marketplace and Maintenance](https://docs.unbrowse.ai/reference/network-layer) for the public explanation of how shared route reuse creates freshness, validation, attribution, and maintenance requirements over time. ## What Ships Today Unbrowse today is a local-first web capability layer for agents: * local CLI plus local server * browser capture through Kuri * reverse-engineering of internal API endpoints from observed traffic * marketplace-backed reuse of discovered skills * route cache plus marketplace search plus live-capture fallback * local credential storage and auth reuse * MCP server mode plus host integrations for major agent environments * reliability scoring, verification, and schema-drift-aware endpoint health * x402-gated marketplace search/execution paths, HTTP 402 payment requirements, wallet-linked payment metadata, and current payout routing * canonical product evals in this repo ## What To Read First Read [Unbrowse In Plain English](https://docs.unbrowse.ai/start-here/plain-english) if you want the shortest narrative explainer in normal language. Read [For Technical Readers](https://docs.unbrowse.ai/by-audience/for-technical-readers) if you want the current architecture, eval truth, and paper-vs-product boundary in one place. Read [For Investors](https://docs.unbrowse.ai/by-audience/for-investors) if you want the market framing, compounding product loop, and the clean line between shipped product and roadmap. Read [System Today](https://docs.unbrowse.ai/reference/system-today) if you want the current product. Read [What Is Unbrowse?](https://docs.unbrowse.ai/start-here/what-is-unbrowse) and [How It Works](https://docs.unbrowse.ai/start-here/how-it-works) if you want the narrative explainer layer that used to live in the old docs set, now rewritten against the current repo and whitepaper. Read [Paper vs Product Status](https://docs.unbrowse.ai/reference/paper-vs-product) if you want the strict audit: shipped, partial, or `coming soon`. Read [Coming Soon](https://docs.unbrowse.ai/reference/coming-soon) if you care about the parts of the route economy that are still forward-looking: richer multi-party fee splits, fuller attribution, validator attestation, and the rest of the paper beyond the shipped payment lane. ## Citation ```bibtex @misc{tham2026internal, title = {Internal APIs Are All You Need}, author = {Lewis Tham and Nicholas Mac Gregor Garcia and Jungpil Hahn}, year = {2026}, note = {Official Unbrowse whitepaper with implementation-aware companion docs} } ``` --- # 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/readme.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.