Skip to main content
Your browser agent can navigate a website and still struggle to get work done. A site might block its traffic, present a CAPTCHA, or require a login before it can reach the page it needs. Browserbase brings Browsers, Verified, Agent Identity, Proxies, and CAPTCHA solving into one platform. Once your agent reaches a site, Secrets and Contexts help you manage credentials and reuse login state.

​
Reach websites that block automation

Websites use browser signals, IP addresses, and challenges to decide which traffic to allow. A browser that works on one site may encounter a block or CAPTCHA on another. Start with the capability that addresses what your session encounters:

Verified

Help your agent access protected sites with a purpose-built browser and real browser fingerprints that Browserbase’s bot-protection partners recognize.

Proxies

Route traffic through managed residential proxies or your own proxies. Choose a location when your workflow needs regional content or consistent geolocation.

CAPTCHA solving

Solve supported CAPTCHA challenges automatically so your browser session can continue. Browserbase enables CAPTCHA solving by default.
You can combine these capabilities in the same browser session. Enable proxies when creating a session, add Verified for protected sites, and listen for CAPTCHA solving events before continuing past a challenge.
Browserbase offers Verified only on the Scale plan. You can start with standard browsers and proxies, or contact Browserbase to request a Verified trial.

​
Give websites a way to recognize your agent

Agent Identity helps participating websites recognize your browser traffic through Web Bot Auth. Browserbase works with bot-protection partners and supports cryptographic identity signals so websites can make access decisions about browser agents. A valid signature identifies traffic; the website still decides whether to allow, challenge, rate-limit, or block it. Web Bot Auth doesn’t sign your agent into a user account. Learn about Web Bot Auth and request beta access.

​
Sign in and stay signed in

Reaching a website doesn’t give your agent access to a user’s account. Your workflow may need credentials, an OAuth flow, or a person to complete two-factor authentication. By default, each Browserbase session starts with fresh browser data, so a later session may need to sign in again. Use Secrets for credentials your Function needs and Contexts for browser state you want to reuse:

Secrets

Store encrypted credentials outside your Function code. Attach a Secret to the Function that needs it, then read its value at runtime.

Contexts

Save cookies and application data after signing in, then reuse that Context in later browser sessions to reduce repeated logins.

​
Start with one authenticated session

  1. Create a Context. Pass its ID when creating a browser session and enable persistence to save changes from that session.
  2. Complete sign-in. If your workflow runs in a Function, attach the required Secrets and read them from context.secrets. For interactive sign-in or two-factor authentication, use Session Live View.
  3. Save and reuse the session state. Close the session, wait a few seconds for the Context to synchronize, then pass the same Context ID to your next session.
A website can expire a login or require authentication again. Your agent still needs the account permissions required for its task. See website authentication for sign-in flows and Secrets in Functions for credential setup.

​
Next steps

Get started with Verified

Configure Verified browser sessions to help your agents access protected websites.

Get started with Contexts

Create a Context and reuse cookies and login state across browser sessions.