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

# Unblock your agents

> Help your browser agent reach protected websites, sign in, and reuse authentication across sessions.

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](/platform/browser/core-features/overview), [Verified](/platform/identity/verified-customization), [Agent Identity](/platform/identity/overview), [Proxies](/platform/identity/proxies), and [CAPTCHA solving](/platform/identity/captcha-solving) into one platform. Once your agent reaches a site, [Secrets](/platform/secrets/overview) and [Contexts](/platform/browser/core-features/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:

<CardGroup cols={3}>
  <Card title="Verified" icon="shield-check" href="/platform/identity/verified-customization">
    Help your agent access protected sites with a purpose-built browser and real browser fingerprints that Browserbase's bot-protection partners recognize.
  </Card>

  <Card title="Proxies" icon="globe" href="/platform/identity/proxies">
    Route traffic through managed residential proxies or your own proxies. Choose a location when your workflow needs regional content or consistent geolocation.
  </Card>

  <Card title="CAPTCHA solving" icon="puzzle-piece" href="/platform/identity/captcha-solving">
    Solve supported CAPTCHA challenges automatically so your browser session can continue. Browserbase enables CAPTCHA solving by default.
  </Card>
</CardGroup>

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.

<Note>
  Browserbase offers Verified only on the Scale plan. You can start with standard browsers and proxies, or contact [Browserbase](mailto:hello@browserbase.com) to request a Verified trial.
</Note>

### 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](/platform/identity/web-bot-auth).

## 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:

<CardGroup cols={2}>
  <Card title="Secrets" icon="key" href="/platform/secrets/getting-started">
    Store encrypted credentials outside your Function code. Attach a Secret to the Function that needs it, then read its value at runtime.
  </Card>

  <Card title="Contexts" icon="browser" href="/platform/browser/core-features/contexts">
    Save cookies and application data after signing in, then reuse that Context in later browser sessions to reduce repeated logins.
  </Card>
</CardGroup>

### 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](/platform/browser/observability/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](/platform/identity/authentication) for sign-in flows and [Secrets in Functions](/platform/functions/secrets) for credential setup.

## Next steps

<CardGroup cols={2}>
  <Card title="Get started with Verified" icon="shield-check" href="/platform/identity/verified-customization">
    Configure Verified browser sessions to help your agents access protected websites.
  </Card>

  <Card title="Get started with Contexts" icon="browser" href="/platform/browser/core-features/contexts">
    Create a Context and reuse cookies and login state across browser sessions.
  </Card>
</CardGroup>


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