Whitepaper: 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
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 soonbeyond the shipped payment laneWhich 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
Recommended Reading Order
Start with For Investors or For Technical Readers for the public/product truth.
Read Marketplace and Maintenance 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
route discovery that maps a site's internal API endpoints into reusable routes
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 if you want the shortest narrative explainer in normal language.
Read For Technical Readers if you want the current architecture, eval truth, and paper-vs-product boundary in one place.
Read For Investors if you want the market framing, compounding product loop, and the clean line between shipped product and roadmap.
Read System Today if you want the current product.
Read What Is Unbrowse? and 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 if you want the strict audit: shipped, partial, or coming soon.
Read 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
Last updated