<!-- llms.txt: https://workos.com/llms.txt -->
<!-- feedback.md: https://workos.com/docs/feedback.md -->

# Agent Vault

Agent Vault lets AI agents work in a browser that is signed in to a website with a login one of your users saved. The agent never receives the password.

Read more in the [Agent Vault guide](https://workos.com/docs/agent-vault).

## Acting for a user

Every Agent Vault endpoint acts for one user. Along with your [API key](https://workos.com/docs/reference/api-authentication), each request names the user, and the organization when the user works in one:

- A request with a JSON body sends `user_id` and `organization_id` in the body.
- A `GET` or `DELETE` request sends them as query parameters.

Saved logins and Spaces belong to the user within that organization, so send the same `organization_id` that the widget token was created with. WorkOS checks that the user belongs to the environment the API key is for and, when an organization is named, that the user is an active member of it. When either check fails, the request responds with `401 Unauthorized`.

Agent Vault is in preview and works in staging environments. Until it is enabled for your team, every endpoint responds with `404 Not Found`.