1. Search returns ranked URLs with titles and descriptions so your agent lands in the right place on the first try.
Primitives
The Search and Fetch APIs let agents see and gather context on the web before acting on it.
Most agent tasks start with a question: where should I go, and what's there?
Most search APIs are designed around how people browse. Agents don't browse. They navigate, extract, and act, and every unnecessary hop costs tokens, time, and reliability.
Most tools return what a page looks like in theory. The Fetch API returns what's actually there. Pass a URL, choose your format, and get back clean, structured content your agent can use immediately.
1. Search returns ranked URLs with titles and descriptions so your agent lands in the right place on the first try.
2. Fetch’s sync response design makes it trivial for LLMs to use. Request a page, get content back. No polling, no callbacks.
3. Browse: Once your agent knows where to go, it still has to get there and do something. Log in. Fill out a form. Download a file.
One API Key gives your agents access to the whole web.
import { Browserbase } from "@browserbasehq/sdk";
const bb = new Browserbase({ apiKey: process.env.BROWSERBASE_API_KEY! });
const searchResponse = await bb.search.web({
query: "a web browser for ai agents",
numResults: 10,
});
const response = await bb.fetchAPI.create({
url: searchResponse[0].url,
});
Point an agent at a topic and get back ranked, readable content. No scraping, no brittle selectors.
Search for a company or contact, pull the right page, extract what you need. Structured, at scale.
Search for what's changing in your space. Pair with a browser session to go deeper when it matters.
Build, ship and scale on Browserbase