Unbrowse Start for free

The browserless
browser.

Permissionless connectors to any application for your agents.

Start for free Read the paper
runbrowser → indexed
unbrowse.run
task     export the March invoices
result   verified
skill    records.export
route    POST /api/exports
         GET  /api/exports/{job}
         GET  /api/exports/{job}/file

Internal APIs Are All You Need · arXiv:2604.00694

3.6×mean speedup in the paper, 94 domains

5.4×median against a fresh browser

1stcall fulfills the task and indexes the route

First-party APIs are the calls the application already makes. Unbrowse learns those, checks them, and hands an agent a skill. The browser is the cold path, not the product.

Read the paper

Same application. Three views.

Your space

  1. public.directory.list Public filings. No password. Ready.
  2. records.search Invoices in an account you connected.
  3. records.export One verified file from that account.

Then the registry

Connectors you could authenticate on the fly sit one step behind. They are not access. billing.vendor.export stays there until the vendor account is connected.

$10

per 10,000 calls. $0.001 each.

Start for free

Install the skill. Don't drive a browser.

export UNBROWSE_URL=https://v2.unbrowse.ai
node skill/scripts/unbrowse.mjs signup --label agent
node skill/scripts/unbrowse.mjs search --intent "export my invoices"

The helper stores the token outside the skill. MCP exposes unbrowse_run and, when only a few skills or choices are open, those options as tools. YAML descriptions are the search text.

Start for free

A token is issued for this browser session. It is not a website password.

Not every site. Not every human check. Not an exact-once promise on an arbitrary website. The run says what was verified, what is unknown, and what was refused.