Browser Tokens let you use sensitive data in browser automation workflows without exposing that data to your application code, agent, or browser infrastructure. They're ideal for agentic workflows that need to enter sensitive values into third-party websites. For payment flows, that value is usually a card number or CVV. For account access flows, it can be a password, recovery code, API key, or any other credential that shouldn't reach your agent, browser platform, logs, or automation code.

We'll briefly cover the flow for using Browser Tokens, but we have several other resources that have more details.

• Launch blog

• Product page

• Pricing

• Integration docs

Browser Tokens workflow

In short, your service passes token values to the browser agent, the agent fills them into the page, and Evervault's browser proxy swaps them for plaintext on the way to an allowed hostname.

1. Collect and encrypt sensitive data: use Card Collection or Relay to collect and encrypt sensitive values. Encrypted values are non-sensitive, so you can store them in your existing database. You can also provide plaintext values directly when that suits your integration.
   
   

2. Create Browser Tokens: send sensitive values to POST /browser-tokens with policies that define where the values can be revealed, and optional egress configuration.
   
   

3. Pass token values to your browser automation: Evervault returns format-preserving tokens that look like the original data, so card tokens are Luhn-valid and preserve the original BIN.
   
   

4. Launch your browser through Evervault's proxy: route the session through the browser proxy using the returned credentials. This works with platforms such as Browserbase, Browserless, Kernel, and Steel, as well as local Chromium and Playwright flows.
   
   

5. Evervault replaces tokens over the wire: your browser enters token values into the page. Evervault scans requests sent through the proxy and replaces tokens with the original plaintext, but only for allowed destinations.

Check out our docs to get started.