ContactBook a call

Systems

Poppy 1.0 and what personal agents will ask of you

Sierra released Personal Agent Protocol (Poppy) 1.0 on 13 Nov 2026. What a mid-size business off Shopify should expose to personal agents, and in what order.

Cover for “Poppy 1.0 and what personal agents will ask of you”, with the line: Publish the basics, then add actions with approval.
Publish the basics, then add actions with approval. Image: SBD.

On 13 November 2026 Sierra released version 1.0 of Personal Agent Protocol, which it calls Poppy. It is a standard for how a customer’s personal agent deals with a company, through the company’s own agent, its website and its APIs. The release post says 1.0 follows about five weeks of testing drafts against real websites, APIs and agents, after the introduction on 6 October and a public draft on 9 October.

Two details in the release matter more than the rest for a business deciding what to do this quarter. Meta’s agent, Muse, now has Poppy enabled for all its users and checks for Poppy first on each site it visits. And Shopify has enabled it for every merchant, so each Shopify store publishes a Poppy file automatically. If you sell on Shopify, you have a basic version already. If you do not, your customers’ agents will look for one on your site and find nothing.

The short answer

Poppy is a file and a set of rules that tell a customer's agent what your business offers and how it may sign in on the customer's behalf. Start by publishing what an agent can read without logging in: catalogue, prices, opening hours, booking slots. Add account actions later, behind OAuth scopes the customer approves, with anything irreversible going to a person first.

What Poppy is, from the sources

We have read the release, the two earlier posts and the 1.0 specification. This is what they say, without our interpretation.

  • A company publishes a poppy.json document at /.well-known/poppy.json on its domain. It tells personal agents how to start a session, how to sign in, and which APIs and company agent are on offer.
  • It is built mostly on standards that already exist: MCP, OpenAPI and UCP. APIs can be described as OpenAPI or offered as an MCP server.
  • Sign-in uses OAuth 2.0, so the customer decides what their agent may do and can change or revoke that access later. A company can also offer signed-out sessions with no sign-in at all.
  • Companies can adopt it in stages, starting with the basics. The implementation kit works in milestones, and a company that only offers its website can stop after publishing the file.
  • Industries add to it through extensions. Shopify co-authored the commerce extension, which uses UCP for product search, carts and checkout and has the agent ask the customer before certain actions.
  • The kit includes a validator, a command-line tool that acts as a test personal agent against your deployment.

Sierra lists more than 100 design partners, including Meta, Shopify, Stripe, Walmart, Salesforce and Zoom, and three companies live: Mercury, Synchrony and Turkish Airlines. At Mercury an agent can check balances and review transactions, while payments and transfers go through the account’s approval policy first. At Turkish Airlines an agent can check fares and flight status and look up bookings, and business-class upgrades need approval before payment.

SBD is not one of the partners and has no relationship with Sierra, Meta or Shopify. We are writing about it because our clients will be asked about it.

What it means if you are not on Shopify

Most of the businesses we work with sell through their own site, a booking tool, a quoting process or a customer portal. Nothing publishes a Poppy file for them. Their customers’ agents will still try to find stock, book a slot or chase an order, and today they do it by reading web pages written for people, which is slow and often wrong.

A Poppy file gives those agents a described way in. It does not require you to rebuild the site, and the spec allows a company to offer only its website at first. The work is deciding what to expose, describing it properly and putting permissions around the parts that change things.

What to expose to personal agents

We sort it by how much harm a mistake could do, the same way we scope permissions on our own AI agent builds.

Things anyone may read

The catalogue, prices, availability, delivery areas, opening hours, returns policy and free booking slots. None of it is private and all of it is already on your site, so this is the cheapest part to expose and the part agents will ask for most.

Things a signed-in customer may read

Order status, invoices, past bookings, account balance and delivery tracking. These need the customer to sign in through OAuth and give their agent a read scope. The spec’s example scope names are of the form orders:read, and companies describe each scope in their own terms.

Things a signed-in customer may change

Rebooking, cancelling, reordering, updating an address and raising a return. These get write scopes and, for anything that moves money or cannot be undone, a step where the customer or one of your team approves it. Mercury and Turkish Airlines both route payments through approval, and we would start every business there.

A staged plan

  1. Publish the basics. A poppy.json file that points agents to your public catalogue, booking and policy pages, with no sign-in. Run the validator against it.
  2. Add an MCP server or an OpenAPI description. Give agents structured calls for search, availability and quotes so they stop scraping HTML. This is usually a thin layer over systems you already run.
  3. Add OAuth-scoped account actions. Read scopes first (order status, invoices), then write scopes one at a time, each with its own scope name and a plain description the customer sees when approving.
  4. Add approvals and logging. Anything over a value, anything irreversible and anything touching personal data goes to a person or back to the customer to confirm. Every agent request is logged against the customer and the scope it used.

Steps 1 and 2 can go live in a few weeks for most businesses. Steps 3 and 4 depend on how your accounts and sign-in work today, which is what the audit finds out.

Risks to plan for

Permissions that are too wide. The spec says a company must not grant scopes beyond those requested, but the scopes you define are your decision. One broad account:write scope is easier to build and much harder to defend. We write scopes per action. Our post on how much an AI agent should be allowed to do sets out the rule we use.

No audit trail. When a customer says “I did not cancel that”, you need to show which agent did it, under which session and which scope, and who approved it. Build the log before the first write scope goes live.

Approvals that nobody answers. An approval step is only useful if a named person picks it up within a set time. Decide who that is and what happens when they are away.

Your own agent answering for you. If you also offer a company agent that personal agents can talk to, it needs the same limits as any agent you put in front of customers.

We already run one of these

SBD runs a public, read-only MCP server at https://smallbaydigital.com/api/mcp. Claude, ChatGPT, Cursor and other MCP clients can call our ROI, build-versus-buy, readiness and agent risk tools through it, with no login. It is the same pattern as step 2 above: structured, read-only calls that an agent can use without guessing at a web page.

Getting agent-ready with SBD

We do this as part of our existing services. The $500 audit covers what a personal agent can and cannot do on your site today, what you should expose at each of the four stages and which scopes and approvals each action needs. The build is then priced as usual: from $1,000 for publishing the file and a workflow behind it, $3,000 for an MCP server or internal tool, and $5,000 for a multi-module setup with sign-in, scopes, approvals and logging. Book a call if you want to talk it through first.

Questions we get asked

Do we need Poppy if we are already on Shopify?

Shopify publishes a Poppy file for every store automatically, so the basics are covered. The work left is anything outside Shopify: bookings, quotes, a B2B portal, support.

Is Poppy the same as MCP?

No. MCP is one of the standards Poppy is built on. Poppy adds how an agent finds your offer, identifies itself and signs in on a customer’s behalf, and an MCP server can be one of the interfaces it points to.

Will this replace our website?

The website stays. The spec treats website browsing as one of the ways an agent can interact, alongside APIs and a company agent.

Sources and further reading

  • AI agents
  • Poppy
  • MCP
  • Permissions

Keep reading

Cover for “MCP for business owners, in plain language”, with the line: One standard plug between an AI assistant and your software.

Explainer

MCP for business owners, in plain language

What the Model Context Protocol is, what it changes for a business, official MCP servers from Stripe and HubSpot, and the risks and controls.

Cover for “Bring your own agent and the software you buy”, with the line: Ask every vendor what your agent can read, do and log.

Systems

Bring your own agent and the software you buy

More software now lets your own AI agent read data, receive events and take actions over MCP or an API. What to ask vendors before you sign in 2026 and 2027.

Cover for “How much should an AI agent be allowed to do?”, with the line: Read widely. Write narrowly. Spend with a cap. Escalate when unsure.

Systems

How much should an AI agent be allowed to do?

An agent with an unscoped token dropped a production database and its backups in nine seconds. Our rule: read widely, write narrowly, cap spend, escalate.

Find out what is worth automating

About 95% of AI pilots never reach the profit line. We start with the work your team still does by hand and measure each build by the hours it saves.

See how we work

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com