每个网站，即使没有官方 API 或 MCP，仍然依赖第一方 API 与后台通信。 Unbrowse 调用了这些网站的第一方 API，使代理式浏览比使用浏览器快50-100倍，成本降低95%。

这是托管的Unbrowse服务的开源客户端 （https://unbrowse.ai）：其REST API的@unbrowse/sdk TypeScript客户端，以及 unbrowseCLI在此基础上构建了新数据。

安装代理技能：

联系你的代理人：

在客户端完成OAuth登录。从终端输入：npx unbrowse login（浏览器中的OAuth，无需粘贴），然后npx unbrowse run 'top stories on hacker news'。

安装 ·CLI ·MCP ·SDK ·故障排查

它是如何运作的

1. 发现。 取消浏览搜索您的私人功能，然后创建公共网站注册 已经编译成工具。
2. 运行。 匹配功能会重放网站自有的第一方 HTTP 请求。没有浏览器。 只有当结果被验证时，跑动才算成功。
3. 学习一次。 无匹配：代理在Unbrowse录制的云浏览器（MCP）中完成任务，或 你上传两个HAR录音（unbrowse learn）。取消浏览将请求编译成 一通通话功能。

Unbrowse

Every website, even those without an official API or MCP, still rely on a first party API to talk to their backend. Unbrowse calls these website’s first party APIs to make agentic browsing 50-100x faster and 95% cheaper than using a browser.

This is the open-source client for the hosted Unbrowse service (https://unbrowse.ai): the @unbrowse/sdk TypeScript client for its REST API, and the unbrowse CLI built on it.

Set up every agent on this machine (skills, an always-use rule, MCP):

npx -y unbrowse setup && npx -y unbrowse login

Or tell your agent: set up unbrowse - https://raw.githubusercontent.com/unbrowse-ai/unbrowse/main/llms.txt. Skill only: npx skills add unbrowse-ai/unbrowse --skill unbrowse.

Connect your agent:

claude mcp add --transport http unbrowse https://unbrowse.ai/mcp

Complete OAuth sign-in in your client. From a terminal: npx unbrowse login (OAuth in your browser, nothing to paste), then npx unbrowse run 'top stories on hacker news'.

Install · CLI · MCP · SDK · Troubleshooting

How it works

1. Discover. Unbrowse searches your private capabilities, then a public registry of sites already compiled into tools.
2. Run. A matching capability replays the site’s own first-party HTTP requests. No browser. A run succeeds only when its result is verified.
3. Learn once. No match: an agent does the task in Unbrowse’s recorded cloud browser (MCP), or you upload two HAR recordings (unbrowse learn). Unbrowse compiles the requests into a one-call capability. Next time is step 2.

Passwords stay in the Unbrowse password manager; the CLI never takes one.

More: docs/how-it-works.md · Paper: Internal APIs Are All You Need (arXiv:2604.00694)

Commands

unbrowse login [--key ub_live_…]    sign in (browser OAuth) or store an API key
unbrowse discover            your capabilities, then the public registry
unbrowse run  [--set k=v]    run a task from your IP (--from-unbrowse: from Unbrowse); waits for a verified result
unbrowse resume  k=v…        answer what the run asked for, on the same run
unbrowse scrape                read one page as markdown
unbrowse index                 teach Unbrowse a site: each flow becomes a tool
unbrowse learn a.har b.har          compile two recordings into a capability
unbrowse logins                     saved logins, masked
unbrowse registry [query]           public compiled sites (no account)

All commands: docs/cli.md. Exit codes: 0 ok, 1 error, 2 input required, 3 sign-in or login needed, 4 not verified.

SDK

import { Unbrowse } from "@unbrowse/sdk";
const ub = new Unbrowse(); // UNBROWSE_API_KEY
const run = await ub.wait((await ub.run({ task: "top stories on Hacker News", idempotencyKey: crypto.randomUUID() })).runId);