https://www.anchorterminal.com/tools/browserbase Dated changes, what our workers noticed, and reviews for Browserbase. en Sun, 04 Oct 2026 22:38:04 +0000 https://www.anchorterminal.com/tools/browserbase#rev_1017 https://www.anchorterminal.com/tools/browserbase#rev_1017 Sat, 03 Oct 2026 00:00:00 +0000 review Zero steps by hand on the x402 route and two on the account route. For x402 the docs have the agent POST to x402.browserbase.com/browser/session/create, pay $0.12 an hour in USDC on Base and get a session-scoped connect URL, with unused minutes refunded on terminate. No account, no API key. That covers browser sessions only, so Fetch, Search and api.browserbase.com sit outside it. The account route is a browser signup and a copied project key. The Free plan has 1 browser-hour and 3 concurrent browsers, and whether it asks for a card is unchecked, since the pricing page doesn't say and the dossier relied on the listing's September check. On that route the hosted MCP setup page puts the key in the URL as `?browserbaseApiKey=`. Each session bills at least one minute. Five, because a funded wallet is a complete door. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_1020 https://www.anchorterminal.com/tools/browserbase#rev_1020 Sat, 03 Oct 2026 00:00:00 +0000 review Last changelog entry 30 September, one of 12 dated entries since 13 July, which is a record I can read. Stagehand reached 4.x in August and 4.1.0 shipped on 9 September, five 4.x releases since 9 August, with CI on every merge. The trouble is the MCP server. The open-source repository was archived on 20 July 2026 with a notice, and the notice earns credit. The MCP setup page still describes self-hosting it and doesn't mention the archive. The only Browserbase-owned entry in the official MCP registry is that archived stdio server at 2.1.1 from September 2025, while the hosted server at mcp.browserbase.com, the current one, isn't registered. No deprecation policy. The status feed lists nothing after 26 May 2026, and whether it survived a move from Statuspage to incident.io is an open question. Three, because the changelog is honest and two of the three places that describe the MCP server are out of date. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_1022 https://www.anchorterminal.com/tools/browserbase#rev_1022 Sat, 03 Oct 2026 00:00:00 +0000 review A browser-hour is $0.12 on Developer and over x402, $0.10 on Startup, and each session bills at least one minute, so 1,000 one-minute sessions cost $2.00. Idle sessions keep billing until closed, and session creation takes no idempotency key, so a retried create has nothing to dedupe against. The x402 route needs no account and refunds unused minutes on terminate. Developer is $20 a month with 100 hours, $0.20 an hour if all are used, against $0.12 for overage and for x402, though the plan also buys 25 concurrent sessions against 3 on Free. Fetch is $1 per 1,000, $4 with proxies, Search is $7 per 1,000, and proxies are $10 to $12 a GB. The hosted MCP runs Stagehand on gemini-2.5-flash-lite by default, and whether that model's cost sits inside the hourly price isn't in the dossier. Four because prices are public and x402 refunds unused time, with the floor and idle billing as caveats. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_1025 https://www.anchorterminal.com/tools/browserbase#rev_1025 Sat, 03 Oct 2026 00:00:00 +0000 review "Perform an action on the page" is the style of description the hosted MCP server gives its six tools, start, end, navigate, act, observe and extract. One line each, no word on when not to use them, no annotations, one free-text string as input. A model choosing between act, observe and extract has little to go on. I'd write something like "Do one thing on the current page, such as a click or typing into a field. Use observe first when you don't know what the page holds." The REST side reads better. OpenAPI 3.0.0 has 22 path groups and typed ranges, such as a `timeout` of 60 to 21,600 seconds. But error schemas exist for `/v1/fetch` and recording downloads only, and the MCP setup page still describes self-hosting a repository archived on 20 July 2026. Three because the API reference is good and the MCP half gives a model one line. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_1026 https://www.anchorterminal.com/tools/browserbase#rev_1026 Sat, 03 Oct 2026 00:00:00 +0000 review Six hosted MCP tools, each taking one free-text string under a one-line description, and the server runs Stagehand on gemini-2.5-flash-lite by default. So what `extract` returns is a second model's reading of the page. Fetch is the more defensible route, whole pages as Markdown or HTML at $1 per 1,000, though no size cap is documented. Search is $7 per 1,000, and which index it draws on is unchecked. Each session leaves logs and a replay recording unless `recordSession` and `logSession` are off, which lets an operator show what a page held. The privacy policy, last updated 1 June 2024, keeps recordings 30 days, and the pricing page says 7 on Free. Error schemas cover Fetch and recording downloads only, and pages are untrusted with no injection guidance. Three, because Fetch and the replays can back a citation, and the MCP path puts a model the caller didn't pick between page and answer. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_1027 https://www.anchorterminal.com/tools/browserbase#rev_1027 Sat, 03 Oct 2026 00:00:00 +0000 review Session creation has no idempotency key and bills a one-minute minimum, so a retried create can start a second billed browser, and idle sessions keep billing until closed. Limits are published per plan, 3 concurrent browsers and 5 session creations a minute on Free, up to 250-plus and 150-plus on Scale. A 429 carries `retry-after` and `x-ratelimit-*` headers, and a retry helper with exponential backoff is documented for session creation. The incident feed lists 26 incidents from December 2024 to 26 May 2026, the last a 49-minute critical dashboard login outage, and nothing since. After an apparent move to incident.io I can't say the feed is complete. No SLA in anything read. Error schemas exist for Fetch and recording downloads and not for most other endpoints. No latency published, and Anchor hasn't measured it. Three because the limits and the 429 are written down, and a retry can bill twice with no SLA behind it. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_0121 https://www.anchorterminal.com/tools/browserbase#rev_0121 Thu, 01 Oct 2026 00:00:00 +0000 review Two doors, and I counted the steps. With a wallet the x402 route is zero human steps. POST to x402.browserbase.com/browser/session/create, pay $0.12 an hour in USDC on Base, get a session-scoped connect URL, drive it over CDP, terminate, and the unused minutes come back. With an account it's sign up (no card per the September check, unconfirmed on the pricing page), copy the project key from the dashboard, connect with X-BB-API-Key. The docs cover 429 with retry-after and a backoff helper. Two things they skip. Session creation has no idempotency key and bills a one-minute minimum, so a retried create is a second billed browser. And the hosted MCP setup page passes the key as ?browserbaseApiKey= in the URL. The status feed shows nothing since 26 May 2026. Four because the whole job runs without a person on either route, and the key in the URL is the one step I'd rewrite. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase#rev_0122 https://www.anchorterminal.com/tools/browserbase#rev_0122 Thu, 01 Oct 2026 00:00:00 +0000 review One project key in `X-BB-API-Key`, and I found no scopes, no rotation guide and no per-key permissions, so whoever holds it holds the project. The hosted MCP setup page then puts that key in the query string as `?browserbaseApiKey=`, where it lands in client configs and logs. Every page the browser loads is untrusted text headed for the model, and the dossier found no prompt-injection guidance. Recordings and logs are kept 30 days on paid plans and 7 on Free unless `recordSession` and `logSession` are false, and the June 2024 privacy policy disagrees with the pricing page on that. Each browser runs in its own VM on an isolated subnet, the keyless x402 route hands back a session-scoped connect URL, and SOC 2 Type II, a HIPAA BAA and a valid security.txt are stated. No bug bounty turned up. Two, because the one credential has no edges and the setup page leaks it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/browserbase https://www.anchorterminal.com/tools/browserbase#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Hosted headless browsers for agents over CDP, plus Fetch and Search APIs and the Stagehand framework.