---
title: "Agent Vault gives your agents a signed-in browser for websites without APIs"
description: "Build agentic products with Agent Vault: store users’ website logins and connect agents through a WorkOS-hosted or self-hosted browser. Contact us for access."
url: https://workos.com/blog/agent-vault
published: "Nov 17, 2026"
---

# Agent Vault gives your agents a signed-in browser for websites without APIs

What happens when an AI agent can do the work, but can't get past the login screen?

Your operations agent is preparing the daily shipment report. The last update is inside a freight portal with no usable API. To finish the report, it needs to get through the login screen.

![](https://cdn.prod.website-files.com/621f84dc15b5ed16dc85a18a/6afbba7f7ea9c55be70e1fc7_Agent-Vault-Blog-Purple-Cursor.png)

Agent Vault is a building block for developers creating agentic products. It gives your agents a signed-in browser for websites without usable APIs. Your users save a website login through a WorkOS widget; the agent can then work inside the site without receiving the saved password. If sign-in needs a person, the user can take over and hand the authenticated session back.

## Connect a login, then let the agent work

A user saves the freight portal login through the WorkOS widget. The agent connects through MCP, and Agent Vault establishes a session in a hosted browser. The agent can then gather the shipment updates for the report. The same pattern gives an agent a way to reach the browser-only part of a larger workflow.

Agent Vault stores the login and handles sign-in. Your agent works in the authenticated browser, so your application does not have to put the saved password in its prompt or tool responses.

Saved logins use WorkOS Vault’s encryption under the hood.

## Bring the user in when sign-in needs help

A website may require SSO, a CAPTCHA, a passkey, or another step that the automated sign-in cannot complete. The user can open the live browser, complete that step, and hand the session back so the agent can continue.

If sign-in gets stuck, Agent Vault can retry and fall back to the user when it cannot recover automatically. The user completes the website’s required steps.

In the freight workflow, the user might complete their company's SSO prompt before the agent reads the shipment page. The agent then continues from the authenticated session, rather than asking the user to copy a password into the conversation.

## Choose a WorkOS-hosted or self-hosted browser

Use the built-in WorkOS browser, or connect a browser you operate through your existing browser integration. With a self-hosted browser, Agent Vault still stores your users’ website login credentials; you provide the browser. Choose one browser provider per environment.

## Use browser sessions alongside API integrations

Agent Vault and Pipes cover different ways of connecting an agent to a service. Pipes supplies OAuth-based access tokens for supported integrations. Agent Vault supplies an authenticated browser for websites that do not offer a usable API or OAuth integration.

An application can use both. Its agent could read records through an API where one is available, then use a browser to retrieve information from a portal that only exposes a website. That is part of moving agents from demos into everyday workflows: they have to work with the software a business already has.

## Get started

Agent Vault is launching with access enabled by the WorkOS team; it is not generally available. If you’re building an agentic product, [contact us](https://workos.com/contact) to discuss your integration and request access.
