This week produced a natural experiment: three unrelated organizations published solutions to the same problem — how do you let an AI agent act for you without becoming you — using three different mechanisms. 1Password's approach for Claude keeps credentials out of the model entirely. As the company frames the core question: "Once an agent can click, buy, update, and submit for you, the key question becomes: what identity is it acting under, and what access should it get?" Its answer is a zero-exposure architecture where 1Password remains the source of truth and injects credentials directly into the page — Claude never touches the vault item, password, or one-time code, and access is scoped to the current task and expires when it ends. Dai Nippon Printing took a credentials-based route instead, extending its CATRINA distributed ID platform to agentic commerce. The company frames the gap plainly: with agentic commerce "a new challenge has emerged in confirming and verifying the user to determine 'whose proxy' and 'with what authority' the AI agent is acting." DNP's fix is verifiable credentials that express a user's delegated authority directly to the agent, rather than relying on session-based trust. The third piece is infrastructural rather than architectural: the Linux Foundation announced the operational launch of the x402 Foundation, an open-governance body originally created by Coinbase to steward x402, a payments-over-HTTP standard. The protocol's aim, per the release, is to let payment capability sit inside ordinary 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 members, including Visa, Mastercard, Stripe, AWS, Google, and Coinbase. What's notable isn't any single mechanism — it's that all three map cleanly onto a division of labor nobody coordinated. DNP addresses an agent's authority to act. 1Password addresses its authority to access the credential needed to act. x402 addresses the transaction itself once authority and access are both settled. Read together, they sketch an emerging separation between person, agent, delegated authority, credential, and transaction — five distinct layers that used to collapse into a single login. This matters because the alternative — agents holding raw passwords or shared API keys — has been the default failure mode of agentic tooling all year. None of these three efforts solve the interoperability problem (a DNP-issued credential doesn't obviously compose with a 1Password-scoped session or an x402 payment rail), but the fact that separate commercial and nonprofit actors landed on compatible boundaries, in the same week, without visible coordination, is itself evidence that the shape of the problem is becoming legible across the industry.