The past week produced a clean illustration of how agentic-commerce infrastructure is settling into layers rather than converging on a single standard. Three announcements from 1Password, Dai Nippon Printing, and the Linux Foundation each tackle a different slice of the same problem: an agent acting on your behalf without becoming you. 1Password's approach for Anthropic's Claude keeps credentials out of the model entirely. As the company frames it, the real question once an agent can act on a login page is what identity is it acting under, and what access should it get. Rather than handing Claude a password, the system uses a zero-exposure architecture where the credentials never enter the model or its memory. 1Password stays the source of truth for the secret, and access is granted only at runtime. After biometric approval from the user, 1Password injects the credential directly into the page. Claude never sees the vault item, password, or one-time code. 1Password's CTO put the distinction plainly: the goal is to let a user grant an agent permission to use a credential without letting the agent see it. Dai Nippon Printing addresses a different layer: proving whose proxy an agent is and what authority it holds. DNP's system, built on its CATRINA distributed ID platform, uses 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. The company frames the underlying problem as confirming, for any proxy purchase, whose proxy and with what authority the agent is acting. The third piece is the payment rail itself. The Linux Foundation has launched the x402 Foundation, an open-governance body created by Coinbase to steward a payment standard 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 Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Google, Mastercard, Stripe, and Visa, per the Linux Foundation's release. None of these three pieces alone solves agent identity. What's notable is how cleanly they divide labor: DNP handles the authority to buy, 1Password handles the authority to access the account needed to buy, and x402 handles the transaction itself. That separation — identity, delegated authority, credential access, and payment rail treated as distinct, composable layers rather than one monolithic protocol — is the more durable signal here than any single vendor's launch. It suggests the industry is converging on an architecture pattern even before it converges on a shared spec, and that the actual hard problem (who authorized what, and how do you prove it later) is being solved piecemeal by companies that don't coordinate with each other.