Personal Agent Protocol: Sierra and Meta set rules for AI agents

Sierra and Meta announced the Personal Agent Protocol, an open standard for how a customer's personal AI agent signs in, identifies itself, and gets work done with a business. Shopify, Stripe, Walmart, Genesys, Rocket, and Instinct are named partners. The v0.1 spec lands later this month. If customers are going to send bots to your store, this is the first serious attempt to give you a front door for them instead of a scraper problem.

What actually happened

Per Sierra's announcement, written by co-founders Bret Taylor and Clay Bavor and published October 6:

• Built on OAuth. No new identity system. The agent authenticates with the same authorization standard your login already uses.
• Three levels of access. An agent can act as a guest to check stock or a returns policy. Once the customer signs in, the customer picks read-only or write access.
• One session across channels. A question asked before sign-in and an order placed after it count as one visit.
• Three ways in. Agents can reach a business through its website, through APIs built on MCP and OpenAPI, or by talking to the company's own agent.
• Not in v0.1. Granular per-action permissions, push notifications for order or flight updates, and a payments extension are listed as future work. Design workshops and a reference implementation follow the spec.

The Next Web notes that Stripe and Shopify also back Visa's competing Trusted Agent Protocol. Nobody is betting on one standard yet.

Why it matters for your business

Today, a customer's agent hitting your site looks like bot traffic. You either block it and lose the sale, or let it through and have no idea who it is acting for. A guest / read / write model fixes that: you decide what an anonymous agent sees and what a signed-in one can change.

1. Your login is the integration point. If your auth is a bolted-on plugin with no OAuth support, that is the first thing to fix. Every agent standard on the table assumes OAuth.
2. Decide your write scope now. Which actions should an agent be allowed to take: reorder, change an appointment, cancel? Write that list before a spec forces the question.
3. Expose the guest data cleanly. Stock, hours, policies, and pricing should come from a structured endpoint, not a page an agent has to parse.
4. Do not build to v0.1 yet. Read it when it ships. Payments are not in it, and a rival protocol has the same partners. Build the OAuth and API layer that serves both.

Sources: Sierra, The Next Web, CMSWire.