Identity · CA
Three Separate Efforts Are Converging on an AI Agent Identity Stack
This week brought three distinct pieces of infrastructure addressing the same underlying problem: proving who an AI agent represents and what it's allowed to do, without letting the agent become its human principal for authentication purposes.
1Password published details on its integration with Anthropic's Claude, built on what it calls a zero-exposure architecture. When Claude needs to log into a site to complete a task, 1Password injects the credential directly into the page rather than passing it through the model. As the company put it, the credentials never enter the model or its memory, and 1Password stays the source of truth for the secret, with access granted only at runtime. After autofill, the system checks that secrets weren't exposed on the page. 1Password's CTO framed the design goal directly: the point is to let a user give an agent permission to use a credential without letting the agent see it.
Separately, Dai Nippon Printing has begun offering a digital identity management function for AI agents making proxy purchases in online shopping, built on its CATRINA distributed ID platform and using verifiable credentials to create an environment where only AI agents authorized by the user can conduct transactions based on the user's will and authority.
And the Linux Foundation announced the operational launch of the x402 Foundation, a governance body created by Coinbase to steward x402, an open standard for internet-native payments over HTTP that embeds secure payment capabilities directly into web interactions so that AI agents, APIs, and applications can send and receive payments as seamlessly as they exchange data. The foundation already counts 40 member organizations including AWS, Google, Mastercard, Stripe, and Visa.
What's notable isn't any single announcement but how cleanly they stack: DNP addresses an agent's authority to buy, 1Password addresses its authority to access the account needed to buy, and x402 addresses the transaction itself. Three separate vendors, three separate problems, converging on the same layered architecture without apparent coordination — identity, delegated authority, and payment as distinct, composable layers rather than one vendor's monolithic solution. That's a stronger signal than any one company's roadmap.