Personal Agent Protocol: Agents Get an ID, But Who Checks It?

Amazon blocked Meta's shopping agent Muse for failing to identify itself while browsing. Meta and Sierra answered with an open agent-identity protocol. It only answers who is knocking, not whether the response is fair.

On September 20, 2026, Amazon blocked Meta's shopping agent, Muse, from amazon.com. According to consistent reporting, the reason was that the agent didn't identify itself while browsing — Amazon cited security and user-experience concerns. Two of the largest tech platforms in the industry, each refusing the other's shopping agent entry: that's not a footnote. It's a window into a layer almost nobody has been discussing out loud — who decides whether an agent gets to knock at all. What Muse is, briefly Meta launched Muse in the US on September 8, 2026, followed by Canada in mid-September. The agent books, fills out forms, negotiates, and pays with a stored card — initially through Link by Stripe, with PayPal added as a second payment path on September 22, and Shopify merchants reachable directly in-catalog via Shop Pay. Where a site has no public API, Muse opens a browser and fills out forms the way a human would — exactly what Amazon interrupted on September 20. The response: Personal Agent Protocol In response, Meta and the customer-experience software company Sierra have, according to multiple reports, previewed a Personal Agent Protocol (PAP) — an open, OAuth-based standard meant to let personal AI agents identify themselves to businesses. The idea: a business should be able to tell a legitimate agent acting on a user's behalf from a bot disguised as one, and should get visibility into what that agent does on its site or through its API. Reported partners include Shopify, Stripe, Walmart, Genesys, NiCE, Decagon, and Rocket — sources don't fully agree on the exact roster; one lists Meta itself naming Decagon and NiCE, where another only cites Sierra's partner list. What all sources agree on: OpenAI and Anthropic are absent from the partner list. Maturity is similarly disputed across sources: one dates a draft spec published by Sierra to October 9, 2026; another expects a v0.1 specification only "later in October" — with no license or governance model published yet either way. The bottom line: there is no finished, production-ready standard yet — only a stated direction (OAuth-based sessions) and a still-incomplete partner list. For context on what else has moved since: on October 12, 2026, Meta opened two new models — Muse Wonder and Muse Wonder Full — to developers first, via the Meta Model API and its coding agent, Muse Code; the consumer Muse app gets them later, starting with …

Author
Nexbid Engineering
Published
2026-10-20
Topics
Protocol Commerce, Verification, Agentic