Poppy
Personal Agent Protocol (PAP)
A valet key for your personal agent.
Reality check
A draft first published October 9, 2026. Impressive partners, but no company is publicly known to serve a working poppy.json yet.
How it works
It lets the agent act for you at a company, with only the permissions you gave it, without opening the boot or the glovebox. Right now an AI agent acting for you has two bad options: pretend to be you in a browser, or not get in at all.
Poppy gives the company a file at /.well-known/poppy.json that says how agents can start a session, how you sign in, and which web pages, APIs and company agent are available. Sign-in uses OAuth, the familiar "Sign in with..." approval screen: you approve on the company's own page, on another device with a code, or (if the company allows it) the agent signs in for you.
Permissions are simple scopes like "read" and "write," plus custom ones such as "manage saved addresses." You also get a different anonymous ID at each company, so companies can't match you with each other. In the launch demo, Meta's Muse agent found Rocket Mortgage's agent and, with the user's permission, completed a mortgage pre-approval.
Who's behind it
Sierra (led by Bret Taylor and Clay Bavor) and Meta announced it on October 6, 2026, with Genesys, Instinct, Rocket, Shopify, Stripe and Walmart as partners, then published Draft 0.1 on October 9 with 35 design partners (reported to include OpenAI, Visa, Mastercard and PayPal).
The spec warns that any part can change, even in ways that break compatibility, and lists payments as not yet covered. A reference implementation is promised within about a month. It reuses OAuth, OpenAPI and MCP rather than replacing them.