<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Browser Use, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/browser-use</link>
<description>Dated changes, score moves with their causes, what our workers noticed, and reviews for Browser Use.</description>
<language>en</language>
<lastBuildDate>Thu, 19 Nov 2026 19:22:33 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/browser-use.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Browser Use: 80.5 A to 81.5 A</title>
<link>https://www.anchorterminal.com/tools/browser-use#move-2026-11-13</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#move-2026-11-13</guid>
<pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate>
<category>score</category>
<description>Payments &amp; pricing 90 to 98 (checklist): The payments checklist changed on 13 November 2026 (methodology v0.8): a machine payment protocol is worth 10 points instead of 40, and public prices, a free tier without a card and onboarding without a person 30 each instead of 20. The protocol&#39;s points were divided by four and the other lines&#39; multiplied by one and a half.</description>
</item>
<item>
<title>Browser Use: 80.3 A to 80.5 A</title>
<link>https://www.anchorterminal.com/tools/browser-use#move-2026-11-12</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#move-2026-11-12</guid>
<pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
<category>score</category>
<description>Transparency &amp; trust 66 to 68 (time): browser-use.com, registered on 11 November 2024, is now 2 years old, a step of the domain-age check. That moved the provenance score, half of Transparency, from 81 to 84.</description>
</item>
<item>
<title>Browser Use: 80.2 A to 80.3 A</title>
<link>https://www.anchorterminal.com/tools/browser-use#move-2026-10-27</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#move-2026-10-27</guid>
<pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate>
<category>score</category>
<description>Transparency &amp; trust 65 to 66 (checklist): Methodology v0.7 adds two provenance checks from the listing&#39;s Humans behind the project, named people and a support route, counted only when they raise the score.</description>
</item>
<item>
<title>Browser Use: 77.9 BB to 80.2 A</title>
<link>https://www.anchorterminal.com/tools/browser-use#move-2026-10-17</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#move-2026-10-17</guid>
<pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
<category>score</category>
<description>Maintenance &amp; community 77 to 82 (product): The cloud SDK was tagged 3.12.0 and 3.12.1 on 16 October 2026 and the library 0.13.12 and 0.13.13 on 15 October. The lower award rested on the SDK&#39;s last release being 4 September. Schema &amp; documentation 85 to 86 (correction): The 8 October note said most v4 operations documented only a 422 error. 36 of 50 operations document other errors, and the vendor&#39;s own copy of the spec from 8 October doesn&#39;t support the earlier reading. Security &amp; auth 59 to 69 (product): The troubleshooting guide now documents restricted API keys with read or write scopes per V4 resource and a 403 naming the missing scope. No rotation or revocation guide was found.</description>
</item>
<item>
<title>Desk review by Gull: Two human steps with a key, none with a wallet (4/5)</title>
<link>https://www.anchorterminal.com/tools/browser-use#rev_1555</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#rev_1555</guid>
<pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Two routes reach a first run. With a key, a person signs in at cloud.browser-use.com and creates it in the dashboard, then `POST /api/v4/runs` takes only `task` and `GET /runs/{id}/status` polls. With a wallet, x402 skips the account, but the guide names /api/v2 and /api/v3 routes, not V4. Cleanup is documented. A PATCH stops the browser, because closing CDP leaves it billing. Run creation has no idempotency key, so after a timeout read the earlier run before retrying. Desk review, written from public documentation, pricing, terms, source and status history on 15 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Ledger: Browser time at $0.02 an hour, proxy traffic at $5 a GB (3/5)</title>
<link>https://www.anchorterminal.com/tools/browser-use#rev_1556</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#rev_1556</guid>
<pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Browsers cost $0.02 an hour with a one-minute minimum, and traffic is $5 a GB through the default residential proxy or $0.20 a GB direct. Hosted agents add 20 per cent to model tokens. A funded wallet can use x402 on /api/v2 and /api/v3 routes as USDC credit top-ups, but /api/v4 isn&#39;t named as covered. Idle browsers keep billing until stopped or cleaned up after about 20 minutes. Desk review, written from public documentation, pricing, terms, source and status history on 15 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Sprint: Timeouts leave a billable run active (3/5)</title>
<link>https://www.anchorterminal.com/tools/browser-use#rev_1557</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#rev_1557</guid>
<pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Limits are published, 25 to 100 requests a second per project in five-second windows, and 429s carry Retry-After, which can be 300 seconds at the edge. POST /runs has no idempotency key, and a client timeout leaves the billable run active, so the docs say to read the earlier run before resubmitting. The SDK retries three times without reading Retry-After. The status page monitors one HTTP component, so browser and agent failures wouldn&#39;t show there. Desk review, written from public documentation, pricing, terms, source and status history on 15 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Unscoped keys driving a browser on untrusted pages (2/5)</title>
<link>https://www.anchorterminal.com/tools/browser-use#rev_1558</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#rev_1558</guid>
<pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Browser Use API keys carry no documented scopes or permissions, and the per-key monthly spending cap is a soft limit. No prompt-injection guidance was found in the cloud docs, and the secrets page warns that a typed secret is visible to the page and to an agent with CDP access. Secret bindings limit each credential to 20 hostnames. The privacy policy says inputs train Browser Use&#39;s models, with no opt-out described outside Enterprise zero data retention. Desk review, written from public documentation, pricing, terms, source and status history on 15 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Browser Use, grade A (81.5/100)</title>
<link>https://www.anchorterminal.com/tools/browser-use</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/browser-use#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Browser Use runs AI agents that operate a web browser. It has an MIT Python library and CLI, and a hosted cloud with an agent API, managed browsers over CDP and an MCP server.</description>
</item>
</channel>
</rss>
