> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Browserbase API Guide for GTM Workflows

> Use Search/Fetch for page discovery and retrieval, or an isolated session for direct browser control. Includes SDK V2 examples, schemas, and cost.

## Playbook

# Browserbase Agent Guidance

Use Browserbase Search when you need web results without opening a browser.
Use Browserbase Fetch when you need page content and do not need interaction.
Use sessions when the caller will connect Playwright, Puppeteer, or another CDP
client to a managed browser. Public session creation disables Browserbase logs
and recordings and does not accept contexts, extensions, certificate IDs,
external proxy credentials, project IDs, or arbitrary metadata.

Do not plan workflows around updating a context. Browserbase deprecated API
context uploads and has removed the update endpoint from its API, so contexts
can only be created, read, and deleted.

Do not use Browserbase Agents for customer workflows. Agent runs accept
shared-project resources and sensitive free-form data without a tenant-scoped
provider boundary or a zero-retention control, so Deepline disables this tool.

This connector uses Deepline-managed Browserbase credentials. Customers are
charged Deepline credits. Never expose Browserbase provider spend.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.