This week, a set of separate announcements shows agent identity infrastructure splitting into distinct, composable layers rather than one company trying to own the whole problem. A trio of new developments points toward an identity and trust stack for delegated agency, coming from 1Password, Dai Nippon Printing (DNP), and the Linux Foundation, each of which addresses the same problem from a different angle. 1Password's contribution addresses the credential-exposure problem for Anthropic's Claude. Rather than handing an agent a password, the company built a zero-exposure architecture: when Claude needs to log in somewhere, 1Password injects the credential directly into the page after user-consented biometric approval, and the model itself never sees the vault item, password, or one-time code. Access is scoped to the task and revoked when it ends. The framing from 1Password's CTO is that the fix isn't giving agents your secrets, it's letting a user grant permission to use a credential without the agent ever seeing it. DNP's piece covers a different layer: authority rather than access. The Japanese printing and identity company 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 so that only agents authorized by a specific user can transact on that user's behalf. The stated goal is resolving the question of whose proxy an agent is and what authority it's actually been given, before a purchase clears. The third piece is transactional plumbing. The Linux Foundation announced the operational launch of the x402 Foundation, a new open-governance body originally created by Coinbase to steward x402, an open HTTP-native payment standard letting agents, APIs, and applications send and receive payments the way they already exchange data. The foundation already counts roughly 40 member organizations, including Visa, Mastercard, Stripe, AWS, Google, and Shopify, governing a protocol meant to keep the payment layer of agentic commerce neutral and interoperable rather than locked to one network. What's notable isn't any single release — it's that none of these three tries to solve the whole stack. DNP addresses an agent's authority to buy. 1Password addresses its authority to access the account needed to buy. x402 addresses the transaction itself. That separation — person, agent, delegated authority, credentials, and the transaction — is exactly the kind of layered architecture that's been missing from agent identity discussions, which have tended to conflate authentication with authorization with payment into one unsolved blob. Three vendors moving independently toward the same division of labor is a stronger signal than any one of them shipping a feature.