The problem it names
Meta and Sierra published Personal Agent Protocol on 6 October, an open standard for how a personal AI agent identifies itself to a business and what that business then lets it do. Genesys, Instinct, Rocket, Shopify, Stripe and Walmart are developing it with them.
The diagnosis in the announcement is blunt about how agents work today. “Most personal agents use websites and apps the way people do — loading pages and clicking through forms,” wrote Bret Taylor and Clay Bavor, Sierra’s co-founders. When that fails, the agent falls back to the support line or the web chat. “This can take a long time, and the agent might fail to complete the task.”
The three constituencies want different things. Consumers want the job done right the first time. Brands want to know when an agent is acting for a customer and to decide what it can do. Agent builders want a direct, consistent route into participating companies.
How a session works
The protocol starts on the company’s website, where an agent discovers what is offered and how to reach it. It then opens a session on its user’s behalf, and can begin as a guest — enough, the authors say, to check product availability or ask about a returns policy.
When a task needs account access, the customer signs in on the company’s page or uses credentials already held by their agent, and decides whether the agent gets read-only or write access. The session is built on OAuth, and carries across channels, so a question asked before sign-in and an order change made afterwards count as one visit.
From there the company picks the route: its ordinary web pages, its APIs through standards such as MCP and OpenAPI, or its own agent for anything conversational, such as a warranty claim.
What is not in version one
The v0.1 specification is due later this month, followed by design workshops and a reference implementation. Several of the things that would make agent commerce actually work are listed as future extensions rather than shipped features: finer-grained permissions on specific actions, push notifications so a company can tell an agent that a flight is delayed or an order has shipped, and payments extensions that would let an agent complete a purchase without handling a card number.
That last one matters. Stripe is a named partner and its head of payments is quoted in the announcement, but paying is not part of the first specification.
Why the retailers signed up
The commercial logic is simpler than the technical one. Meta told TechCrunch that “turning away a personal agent means turning away the customer behind it”, and that it would rather work with businesses on the underlying concerns than see them lose that customer.
Tony Bates, chairman and chief executive of Genesys, put the brand side of it this way in the announcement: “Brands need a trusted way to know who an AI agent represents, what it’s authorized to do, its intent, and how to work with it securely.”
What to watch
An open standard is only a standard once more than its authors implement it. The list of names is the strongest thing about this announcement and the specification is the weakest — it does not exist yet. Watch whether the v0.1 text lands this month as promised, whether anyone outside the founding group adopts it, and whether a rival standard from the payments side ends up defining the same handshake first.
