Skip to main content
The Browserbase Search API gives your agents fast, token-efficient web search results as a complement to browser sessions. Use it for recon, lead discovery, or RAG pipelines, then hand off to a browser session for interaction. Send a POST request to /v1/search with your query. Authenticate with the same x-bb-api-key header used across the Browserbase API.

Request parameters

Response

Each result object contains:

Combining search with browser sessions

A common pattern is using the Search API to find relevant URLs, then opening them in browser sessions for deeper interaction, such as extracting content, filling forms, or taking screenshots.

Rate limits

The Search API is rate limited to 120 requests per minute per project. Exceeding this returns a 429 status code.
For high-volume use cases, space out your requests or implement exponential backoff in your retry logic.

Error handling

SDK
Use Search when your browser agent doesn’t yet know where the information lives. In other words, it will give you the best starting points on the web for some task. Think about Search -> Fetch -> Browsers
  • Search: Find relevant sources (website, news, docs).
  • Fetch: Quickly extract content from most pages, and filter out low-value results.
  • Browsers: Log in to portals with agent identity, navigate complex pages, and extract the hard-to-reach data.

Need more help deciding which API?

Read our full guide breaking down which API to use with examples.