Three announcements landed within days of each other, and together they sketch an emerging architecture for AI agents acting on someone's behalf — one that deliberately separates identity, authority, credentials, and payment into distinct layers rather than collapsing them into a single login. 1Password published details on its integration with Anthropic's Claude built on what it calls a zero-exposure architecture. 1Password acts as an authority to step in and authenticate a user without disclosing unnecessary information, and when Claude needs to sign in, 1Password shows the user which credential is being requested and why. The credential itself never touches the model. As 1Password's CTO put it in the piece, the goal isn't handing agents your secrets but letting a user grant permission to use a credential without letting the agent see it. Separately, Dai Nippon Printing rolled out a digital identity function for AI agents making proxy purchases, built on its CATRINA distributed-ID platform and using verifiable credentials. The stated aim is to create an environment where only agents authorized by the user can transact based on that user's actual will and authority — addressing the question of whose proxy an agent is acting as, and under what scope, before a purchase clears. The third piece is structural rather than technical: the Linux Foundation announced the operational launch of the x402 Foundation, an open-governance body created by Coinbase to steward the x402 protocol for internet-native payments over HTTP. The protocol embeds payment capability directly into web interactions so agents, APIs, and applications can exchange payment as easily as data, covering everything from cards to stablecoins. The Foundation already counts roughly 40 member organizations, including Amazon Web Services, American Express, Circle, Cloudflare, Google, Mastercard, Stripe, and Visa. What makes this notable isn't any single launch — it's that the three map cleanly onto separate layers of the same problem. DNP handles an agent's authority to buy. 1Password handles its authority to access the account needed to buy. x402 handles the transaction itself. None of the three vendors is claiming to solve identity, authority, and payment in one shot; each is explicitly scoping itself to one layer and expecting the others to be handled elsewhere. That's a meaningful design choice given how many agent-identity proposals over the past year have tried to bundle authentication, authorization, and settlement into a single credential. It's also a bet that delegated authority for software acting as your proxy needs the same separation of concerns that human identity systems eventually settled on — you don't want the thing doing the clicking to also be the thing holding the keys.