Skip to main content
Agent Vault lets an AI agent check out and sign in on your behalf. Your real card number and passwords are kept in a vault and typed into the site only at the moment of a fill. The agent is handed only placeholders, never the real values, with one narrow read-back exception for text a site echoes back onto the page.

​
Connect your agent

Agent Vault works with the agents you already use. Pick yours to set it up in about 2 minutes, with no API key to copy.
ImageMeta MuseImageGrok BotImageOpenClawImageClaude CodeImageHermesImageClaude DesktopImageAntigravityImageCodex
Using another agent? Any MCP client that supports streamable HTTP and OAuth can connect. See Connect your agent.

​
How it works

  1. You add your card, addresses and logins to the vault from the dashboard.
  2. Your agent receives mock tokens instead, such as av_card_1_number_u7x2k. They mean nothing anywhere else.
  3. The agent drives a browser that runs inside the Agent Vault proxy, and fills checkout and sign-in fields with tokens.
  4. At each fill, the proxy checks your rules, swaps the token for the real value, and types it into the merchant’s page. The merchant gets the real value. The agent never does.
Agent sends a mock token to the proxy; the proxy resolves it and types the real value into the merchant page.Agent sends a mock token to the proxy; the proxy resolves it and types the real value into the merchant page.

The agent sends a token. The proxy types the real value into the page at the last moment.

A stolen token only works inside the proxy, for the account that owns it. A login fills only on its registered site, your other details only on a site you authorized, and a card only within its agent card’s limits. A card with no agent card has no spending caps or merchant rules, only your plan’s payment quota. How it works follows one checkout step by step, and the Security model sets out what an attacker gets.

​
Who it is for

Account holders

You want an agent to buy things or sign in for you, and you want to decide how much it spends, where, and when it asks you first.

Developers

You are building an agent that pays or signs in, and you want no card numbers or passwords in its prompts, logs or tool output.

​
Safer than giving each agent its own card

A virtual card per agent caps spending, but the agent still holds a working card number. Anyone who gets that number out of the agent’s context can use it.

​
What you control

Spending limits

Caps per transaction, per day, per week and per rolling 30 days.

Merchant rules

Block specific sites, or on Enterprise, allow only the sites you name.

Purchase approval

Above an amount you choose, the checkout waits for your yes.

Human handoff

Bank checks, one-time codes and CAPTCHAs come to you on the live page.

Kill switch

Stop every agent in one click.

Activity log

Sessions, fields filled by kind, and refusals with their reasons, recorded on a best-effort basis.
An agent card holds these rules on top of your own card. It has no card number of its own. See Agent cards.

​
What Agent Vault is not

​
Who makes Agent Vault

Agent Vault is a product of SocialConnect Labs, Inc., doing business as Self Labs, the company behind Self. The company publishes its Terms of Service and Privacy Notice on self.xyz. Questions about either, or about Agent Vault’s own terms, go to team@self.xyz.

​
Next steps

Quickstart

From sign-up to your agent’s first checkout, in about 15 minutes.

Core concepts

The terms the rest of the docs use.

Choose an integration

MCP server, Playwright SDK, or the agent skill.

FAQ

Short answers to the questions new users ask first.