🧭 StackPilot
AI Agents · October 2026

Poppy Agent Protocol: What Small Businesses Should Do Now

Disclosure: Some links on this page are affiliate links. If you buy through them, StackPilot may earn a commission at no extra cost to you. Learn more.

Meta and Sierra published a draft standard for how customers' AI agents identify themselves and act on business accounts. It is early, but it shows where agent-to-business traffic is heading.

By StackPilot Team· October 18, 2026· 5 min read
âš¡ TL;DR

What was announced

According to secondary coverage of the announcement, Meta and Sierra unveiled the Personal Agent Protocol at Sierra's summit on October 6, 2026, and released a first technical draft (version 0.1) on October 9, along with 35 additional design partners. We have not reviewed the official specification directly, so treat details below as reported, and check the spec itself before building anything.

The problem it targets is simple. Customers are starting to use personal AI agents (Meta Muse and OpenAI Dots are two recent examples we have covered) that need to deal with businesses: check an order, request a return, change a booking. Today those agents often have to pretend to be a person logging in. Poppy proposes a standard way for an agent to identify itself and for a customer to grant it limited, revocable access to their account.

How it reportedly works

Reported gaps: payments, push notifications and attachments are not finished in the draft. Visa, Mastercard, PayPal and Adyen are reportedly among the partners, but the draft is not described as a complete payment framework.

Who is involved, and what that does not prove

Launch partners reportedly included Genesys, Rocket, Shopify, Stripe and Walmart. The October 9 list of 35 design partners reportedly includes tools small businesses already use, such as Zapier, Notion, Klaviyo, Zendesk and Cloudflare, alongside banks, retailers and airlines. Design partners give feedback on a draft. That is not the same as shipping support, and no production adoption figures, certification program or benchmarks have been published that we could find.

What this means for a small business

For a typical small business, nothing needs to be built this month. Implementing the protocol means running authentication, session management and authorization enforcement, which is real engineering work. Coverage suggests adoption will mostly depend on whether e-commerce platforms, customer-service vendors and identity providers add support on your behalf. That is the realistic path: you inherit it from your stack.

What is worth doing now is cheap and tool-agnostic:

Risks to keep in mind

Reporting on the draft notes that an agent can claim a user approved something without the business being able to prove the user saw the terms, and that an agent acting beyond the customer's intent is not solved by authentication alone. A mediated sign-in option, where the agent submits credentials to a designated endpoint, is reported to carry more risk. Security will depend on implementations, not on the spec.

How it fits with automation tools

If agent access becomes common, the automation layer you already use matters more, not less. Workflow tools such as Zapier and Make are where approval steps, logging and routing happen today, and a human-approval step is exactly the kind of control the protocol leaves to implementers. For the pricing side of AI steps, see our Make vs Zapier comparison.

Bottom line

Poppy is worth knowing about because large platforms are lining up behind a common way for agents to deal with businesses. It is not worth building against yet. Watch for the reference implementation and design workshops Sierra reportedly plans for next month, and for support announcements from the platforms you already pay for.

Sources: coverage from Audit Commons and Data Studios on the October 6 and 9, 2026 announcements. Details may have changed; verify against the official specification.

Related guides