Proof Launches x401: A Digital ID System for AI Agents That Spend Money
AI agents are starting to shop, book, and transfer money on our behalf. But when an agent shows up at a checkout page, the merchant has no reliable way to know whose orders it’s really following. On October 15, identity company Proof launched x401, an open protocol designed to fix exactly that — verified legal identity and transaction authorization for AI agents, live in production from day one.
What x401 does
x401 is an open HTTP protocol that lets any website ask an AI agent two questions: who are you acting for, and what did that person approve? Three capabilities are live today:
- An agent identity wallet, held by the consumer, that stores their verified legal identity and shows exactly what information and transaction terms are being requested.
- The x401 protocol itself, for requesting and verifying identity and authorization evidence.
- A production Model Context Protocol (MCP) server, compatible with Meta’s Muse, ChatGPT dots, Grok, Claude, and other assistants that support MCP.
The flow works like this: you approve an action — say, a purchase or a wire transfer — on your own device. Your wallet signs the request with a cryptographic signature tied to your verified identity. The AI agent carries that signed request to the merchant, which can independently confirm your identity and check the signature on the transaction itself. If the agent alters the amount, the recipient, or any other signed term, the signature no longer validates and the merchant can tell.
Why this matters now
The launch comes weeks after Amazon blocked Meta’s Muse agent from its marketplace on September 21, citing concerns that the agent did not identify itself, appeared to collect customer credentials, and moved through accounts and transactions without Amazon’s knowledge or consent. Meta had released Muse on September 8; it quickly reached No. 1 on the U.S. App Store, and Shopify connected its Shop Pay checkout.
The Amazon episode exposed what Proof calls the “Agent Evidentiary Gap”: an agent may hold a valid password, OAuth token, API key, or payment card, but none of those prove that the person behind it authorized a particular action. For merchants, that gap means fraud and dispute risk. For banks, lenders, and insurers, it raises questions about legal identity, consent, and enforceability.
Consumers are uneasy, too. In a survey of 1,000 U.S. consumers by Exploding Topics cited in the announcement, 31% said they would not let an AI agent spend any money on its own, and 51% were uncomfortable with AI tools storing their card details.
The launch also follows September guidance from FinCEN and federal banking regulators recognizing digital certificates and verifiable credentials, under certain conditions, as a permissible way for banks to verify customer identity — a regulatory tailwind for the approach Proof is taking.
The practical angle: what you could actually do with it
Today, giving an AI agent spending power mostly means handing over your credentials and hoping for the best. With an identity wallet model, you could authorize a specific itemized purchase or payment mandate on your own device, without the merchant ever needing your password — and without the agent being able to quietly change the terms after you approve.
For businesses, the pitch is lower friction too: websites can request verified identity claims without a sales process or a negotiated agreement, with the option to pay per claim over the x402 payment protocol. Developers can deploy x401 today using the published protocol, identity scheme, implementation guides, and reference implementation.
Analysis: promising infrastructure, but adoption decides everything
The technology is sound — identity wallets and signed credentials are well-established tools, and Proof is no newcomer: the company operates a WebTrust-audited certificate authority, created the online notarization category with the Notarize Network, and says more than $1 trillion in transactions have been secured on its platform across mortgage, automotive, wealth, insurance, and enterprise markets.
But protocols win or die on adoption. x401 only works if websites implement the requesting side and if the big assistant platforms support the MCP server well. The Amazon–Muse standoff shows merchants want control over how agents access them — some may simply prefer their own closed agent systems over an open protocol. Whether x401 becomes the shared ID layer of the “agentic web” or remains a niche tool will be decided by developer and merchant uptake over the next year, not by the launch announcement itself.
Frequently asked questions
What is x401?
x401 is an open protocol launched by Proof on October 15, 2026, that lets any website verify an AI agent’s identity and confirm the human behind it authorized a specific transaction. It centers on an agent identity wallet that stores a person’s verified legal identity and signs each action with a cryptographic signature. If the agent changes the amount, recipient, or other signed terms, the signature no longer validates.
Which AI assistants does x401 work with?
Proof says x401 works with Meta’s Muse, ChatGPT dots, Grok, Claude, and other assistants that support the Model Context Protocol (MCP). A production MCP server is live alongside the protocol, so developers can integrate identity verification into agent workflows using standard MCP tooling.
Why did Proof build x401?
The launch follows Amazon’s September 21 block of Meta’s Muse shopping agent from its marketplace, which exposed the lack of any reliable way for businesses to verify who an AI agent acts for or what that person authorized. Proof describes this as the “Agent Evidentiary Gap”: access credentials like passwords and payment cards don’t prove authorization for a specific action. September guidance from FinCEN and banking regulators on verifiable credentials added regulatory momentum.
Is x401 a consumer product or developer infrastructure?
It’s infrastructure. Consumers interact with the agent identity wallet to approve actions on their own device, but the real adoption story is on the developer and merchant side: websites implement x401 to request verified identity claims, and can pay per claim over the x402 payment protocol. Reference implementations and guides are available for developers deploying it now.
Sources
- Proof launches x401, giving AI agents a way to prove who they represent — GlobeNewswire, Oct. 15, 2026 (official announcement)
- AI Agent Identity Gets x401 Protocol From Proof — GenZ NewZ, Oct. 15, 2026 (independent reporting on the announcement)
Related reading on USABite: AI Agents for Business Automation: What They Are and How They Work.
