Three separate announcements over the past few days show the same problem being attacked from different angles: how do you let an AI agent act for you without letting it become you. 1Password published details on its integration with Anthropic's Claude built on what it calls a zero-exposure architecture. The company frames the core question plainly: once an agent can click, buy, update, and submit for you, what identity is it acting under, and what access should it get. In its design, Claude can complete browser logins and one-time-passcode flows, but credentials never enter the model or its memory — 1Password stays the source of truth and injects credentials directly into the page after user-consented biometric approval, so the agent knows it used a login without ever seeing the password or code. Separately, Dai Nippon Printing has begun offering a digital identity management function for AI agents making proxy purchases, built on its CATRINA distributed ID platform and using verifiable credentials. DNP frames the gap directly: with agentic commerce, a new challenge has emerged in confirming whose proxy and with what authority an agent is acting. Its answer is to extend existing identity-verification and access-control infrastructure to agents so that only agents explicitly authorized by a user can transact on their behalf. The third piece is governance rather than product. The Linux Foundation announced the operational launch of the x402 Foundation, an open-governance body created by Coinbase to steward x402, a protocol that embeds payment capability directly into HTTP so agents, APIs, and applications can send and receive payments the way they exchange data, spanning card rails to stablecoins. The Foundation already counts roughly 40 member organizations, including premier members Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Ripple, Shopify, Stripe, and Visa. What's notable isn't any single launch but how cleanly the three map onto distinct layers of the same 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. None of the three claims to solve agent identity alone — each is scoped to one link in a delegation chain that, until recently, was handled by handing an agent your password and hoping for the best. The direction is toward separating person, agent, delegated authority, credential, and transaction into distinct, independently verifiable pieces rather than one broad trust check. This is still assembly, not a finished system. Verifiable-credential-based delegation, zero-exposure credential injection, and an HTTP-native payment layer are being built in parallel by different vendors with no single interoperability guarantee between them yet. But the shape of the stack is now visible in shipping product, not just white papers.