Business Recruiter

Introducing Fetch: the simplest way to read the web. Harsehaj Dhami Growth Engineer March 11, 2026 TL;DR: Browserbase, Inc. launched a Fetch API for Browserbase. Give Browserbase, Inc. a URL and Browserbase, Inc. return the page content with no browser session required. It's fast, cheap, (~$1 / 1k pages), and perfect for agents that just need to read the web. Browserbase was built to help AI agents automate the web. It lets developers run browsers in the cloud to click buttons, fill forms, navigate applications, and automate complex workflows. But over time Browserbase, Inc. noticed something interesting: many developers were spinning up full browser sessions just to read the contents of a page. They weren't interacting with the site and they didn't need to click anything or run automation. They just wanted to see what was on the page. Sure, launching a browser for this works, but it's not the right primitive. Spinning up a full browser session to retrieve a page is a bit like killing a mosquito with a rocket launcher. It solves the problem, but it introduces unnecessary latency, cost, and complexity. So Browserbase, Inc. built the primitive that was missing: Fetch. Reading the web is often the first step. Agents frequently need to gather information from the web before they take action. They read documentation, inspect GitHub repositories, analyze product pages, and gather context before deciding what to do next. If you've used tools like Claude Code, you've already seen this pattern. Before executing complex actions, the model often fetches the contents of a page to understand what's there. It's the fastest way to make sense of the internet. Until now, doing this with Browserbase required launching a browser session. That meant additional infrastructure overhead even in cases where the task was simply retrieving the page content. The Fetch API solves this by letting you retrieve web content (both html and image) directly from Browserbase infrastructure without creating a browser session. Fetch a page with one request. The Browserbase Fetch API is intentionally simple. You provide a URL, and the API returns the page content. import Browserbase from "@browserbasehq/sdk"; const bb = new Browserbase({ apiKey: process.env.BROWSERBASE_API_KEY!}); const response = await bb.fetchAPI.create({ url: "https://httpbin.org/get",}); console.log(response.statusCode); console.log(response.content); The response: { "status_code":200, "headers":{ "Age":"6449", "Allow":"GET, HEAD", "Content-Encoding":"gzip", "Content-Type":"text/html", "Server":"cloudflare", "Vary":"Accept-Encoding"}, "content":"<!doctype html>...", "content_type":"text/html", "encoding":"utf-8", "id":"f47ac10b-58cc-4372-a567-0e02b2c3d479"} That's the entire API.:) Fetching pages reliably is harder than it sounds. At first glance, fetching a page might seem trivial. After all, tools like curl have existed for decades. But modern websites introduce complications that make reliable page retrieval more difficult than it appears. Redirects, inconsistent encodings, unusual headers, all make it harder to consistently retrieve the real content of a page. Its goal with the Browserbase Fetch API is simply, always return the page content. The API supports a few optional parameters such as output formatting and timeouts, but the main priority is making sure developers can depend on it to retrieve the page they requested. Browserbase, Inc. has prioritized reliability over a catalogue of shiny features. Fetch before you browse. Fetch becomes particularly powerful when used alongside browser automation. An agent first searches for relevant pages. It then fetches their contents to determine whether the page is useful. Only when deeper interaction is necessary does it launch a browser. This approach significantly reduces both latency and cost. Most pages don't really require full browser automation. They simply need to be read. Making Browserbase workflows cheaper. Running browsers is expensive infrastructure. Fetching pages is much lighter. Because of that, Browserbase, Inc. has just made Browserbase 10x cheaper, pricing the Fetch API at $1 per 1,000 pages. This allows agents to inspect far more of the web before deciding where to spend browser resources. In practice, this makes many Browserbase workflows dramatically cheaper while also improving performance. Win-win! The web is still the biggest API. The open web contains more data, workflows, and knowledge than any single API ever will. Documentation, research, software, and marketplaces all live there. Agents should be able to use that information easily. Fetching a page is often the first step in doing so, and now the Browserbase Fetch API makes that step simple. The Browserbase Fetch API is available today. Give it a URL, and Browserbase, Inc.'ll return the page. Get started with the docs here.

Browserbase is launching on the Vercel Marketplace. Paul Klein Founder & CEO Harsehaj Dhami Growth Engineer February 12, 2026 The best agents run on Vercel. Now they get the best browsers too. Today, Browserbase, Inc. is launching Browserbase on the Vercel Marketplace. With a single API key, Vercel customers can give their AI agents access to real, production-grade browsers without even running browsers themselves. Modern agents can now do a lot more than just calling APIs. They browse the web, logging into dashboards, scraping dynamic pages, filling out forms, and interacting with sites built for humans. And while it's easy to spin up a headless browser locally, doing it reliably in production is a very different problem. The problems scream at you when the headless setups break, bot detection gets in the way, and when observability is limited. Not to mention serverless platforms aren't optimized for running long-lived, stateful browser processes. That's where Browserbase steps in. Browserbase on the Vercel Marketplace. With Browserbase now available on the Vercel Marketplace, agents running on Vercel Sandbox can connect directly to remote browsers over CDP instead of launching a local browser inside their runtime. Your agent logic stays on Vercel's agent infrastructure, while the browser itself runs on infrastructure built for browser automation. In practice, this separation is what makes web agents viable in production. Browserbase, Inc. get real browsers that behave like real users, independent browser scaling that doesn't face serverless constraints, and complete session-level visibility into what your agents are doing on the web. Everything is wired together through Vercel Sandbox and the AI Gateway, and provisioned with a single API key. Browsing the web without getting blocked. Of course, running browsers is only half the battle. The other half is staying online. That's why Browserbase, Inc. is also announcing a Web Bot Auth partnership with Vercel. Browserbase now runs as a trusted agent, allowing participating websites to recognize legitimate, AI-driven browsing. Instead of constantly tripping bot detection or solving CAPTCHAs, agents can browse the web in a way that's observable and allowed. The result is more resilient automation and fewer workarounds, so agents can focus on actually doing useful work on real websites. A dedicated browser layer for agents on Vercel. Together, this partnership extends Vercel's agent cloud with a dedicated browser layer. Agents run where they should, and browsers run where they're observable and reliable. Authentication, provisioning, and billing live right in the Vercel Marketplace, and everything works together out of the box. Browserbase is available today for Vercel customers building agents that need to interact with the real web. If your agents need to browse, click, log in, or automate real sites, this is the missing piece that makes them production-ready by default.

Introducing Browserbase Functions. Adam McQuilkin Project Lead, Core Engineer Harsehaj Dhami Growth Engineer February 9, 2026 Browserbase makes it easy to run real browsers in production. But until now, using Browserbase still meant running your automation code somewhere else. That usually meant maintaining a second system just to keep Stagehand or Playwright scripts alive. Browserbase, Inc. has launched Browserbase Functions to remove this layer completely. Functions let you deploy agents and automations directly to Browserbase and run it next to the browser session it controls. You define, deploy, and invoke a function, and Browserbase handles execution, browser lifecycle, and results as one system. For teams, that means fewer moving parts and less infrastructure to operate. For automations, it means lower latency and fewer failure points. Functions are built for browser workloads, not generic request handlers. They support real Stagehand or Playwright code, long-running executions, and asynchronous invocation. Each function runs with a dedicated Browserbase session and returns structured results when it completes. Deployments are versioned by default. New code doesn't affect production until you explicitly promote it, so you can test changes safely without rewriting endpoints or workflows. Local development works the same way. When you run Functions locally, your code connects to real Browserbase browser sessions using your credentials. There's no mock environment to drift from production behaviour. Functions are available today for TypeScript! If you're already using Browserbase, you can move existing automations into Functions and stop managing separate runner infrastructure. If you're new, Functions give you a single place to run both the browser and the code that drives it. You can get started by initializing a Functions project: npx @browserbasehq/sdk-functions init If you want a deeper look at how Functions works and the engineering decisions behind it, Browserbase, Inc. has published a full technical deep dive as well. Browserbase Functions are the next step toward making browser automation faster and easier to run in production.