AI News

Sierra Releases Personal Agent Protocol 1.0, Shopify All Stores and Meta…

gihyo.jpUpdated Nov 16 21:18

AI summary

On November 13, 2026, Sierra released Personal Agent Protocol (commonly known as Poppy) 1.0 to standardize interactions between personal AI agents and enterprises. All Shopify stores will automatically publish Poppy files, Meta's agent Muse becomes the first supported consumer-grade agent, and Mercury, Turkish Airlines, and Synchrony have also begun using it. The specification requires enterprises to declare available websites, APIs, or enterprise-side agents in /.well-known/poppy.json; APIs can use MCP or OpenAPI, account access requires OAuth authorization, and it supports the UCP commerce extension jointly developed with Shopify; more than 100 companies have participated in its development, and Sierra also provides an implementation suite for enterprises.

Why read this

AI score 82

The protocol splits connection discovery, OAuth authorization, and transaction extensions into specifications that can be implemented in layers, allowing readers to assess the costs and boundaries of enterprise integration with AI agents.

Topics

Tags

Body · AI translation

Sierra, a developer of enterprise AI agents, announced on November 13, 2026, that it has released version 1.0 of the Personal Agent Protocol (commonly known as Poppy), which defines how personal AI agents interact with businesses. All Shopify stores now support it, and with Meta's AI agent Muse, all users can now use Poppy. Mercury and Turkish Airlines have also begun using it.

Releasing Personal Agent Protocol 1.0 - Sierra

Poppy is an open standard whose concept was announced by Meta, Sierra and others on October 6. It defines how personal AI agents, when carrying out shopping, bookings and other tasks on behalf of users, connect with company websites, APIs and companies' own agents. Companies decide which functions they offer to agents. Users can choose the access permissions they grant their own agent, and can also revoke them later.

Shopify and others support it; more than 100 companies helped draft the specification

According to Sierra's announcement, all stores on the e-commerce platform Shopify will automatically publish a Poppy file that tells agents about connection endpoints and functions, so merchants do not need to implement anything additional.

Muse also announced on its official blog the same day that it has become the first consumer-facing agent to support Poppy. According to Sierra, all users can use Poppy with Muse. When Muse visits a site, it first automatically checks whether that site supports Poppy.

According to Muse's announcement, Muse connects through Sierra to the financial services company Mercury, where it can check balances and recent transactions and categorize spending. Users can also ask the agent to make payments or transfers, but before execution Mercury carries out an approval process in accordance with that account's rules.

At the airline Turkish Airlines, users can now check fares and flight status, and look up reservations using a reservation number and surname, through personal agents. Miles&Smiles members can also have the agent look for upgrades to business class, but the member's own approval is required before payment. The company says it is also developing a feature that lets members complete purchases within a conversation with the agent.

Sierra also introduced Synchrony, a provider of consumer financial services, as a company that has begun using Poppy. However, it says that an initiative in which personal agents help users choose products while taking rewards and loan products into account is still under consideration.

Participation in drafting the specification is also expanding, with more than 100 cooperating companies. The published list of participating companies includes Meta, OpenAI, Instinct and Manus, which work on personal agents, as well as the payment services Stripe and Visa, the retailer Walmart and the customer management software company Salesforce.

Common framework for endpoint discovery and account access

Under the Personal Agent Protocol 1.0 specification, companies publish a file at /.well-known/poppy.json on their own domain that describes the connection endpoints and functions available to agents. It lists information such as websites that can be operated, APIs that can be called, and company-side agents that can be conversed with. Companies must provide at least one of these routes, and personal agents read the file and choose which route to use. API-based integration can use MCP or OpenAPI.

In Poppy, when an agent interacts with a single company on behalf of the same user, web operations, API calls and conversations with the company-side agent are handled together as a unit called a session. For an agent to access a customer account, it must obtain the user's permission via OAuth, separately from the session. At that time the user chooses the scope of access to grant, and the agent operates within that scope[1].

Poppy also has an extension mechanism for adding functions for specific uses without changing the core specification. Companies can use officially published extensions or define their own. Supporting extensions is optional, and only those supported by both the company and the personal agent can be used.

One of the official extensions is a commerce extension co-developed with Shopify, which combines Poppy with the Universal Commerce Protocol (UCP). Poppy handles endpoint discovery and account access, while UCP handles processes such as product search, adding items to a cart and payment. With this extension, agents can shop as a guest without logging in, or log in with a customer account. However, depending on the operation, the user's permission may be required before execution.

Reflecting trial results of the draft; an implementation kit for companies is available

Personal Agent Protocol 1.0 reflects the results of about five weeks of trials of the draft by companies cooperating in drafting the specification, using actual websites, APIs and agents. The specification was arranged so that companies can start with basic support and add functions later, and the mechanisms for exchanging procedures and feedback between companies and personal agents were also expanded. For example, companies can guide agents through the order in which APIs needed for things like changing reservations should be called. Meanwhile, if a user's request cannot be handled through Poppy, the agent can report that to the company.

Regardless of whether they participated in drafting the specification, any company can make its own systems Poppy-compatible. The implementation kit for companies that supports this work includes skills that convey work procedures to coding agents and verification tools that check the implementation. The coding agent investigates existing systems according to the skills and proceeds with the design and implementation needed for Poppy compatibility. The verification tool connects to the target system as a test personal agent and can check which requirements of the specification are met.

Poppy also has an extension mechanism for adding functions for specific uses without changing the core specification. Companies can use officially published extensions or define their own. Supporting extensions is optional, and only those supported by both the company and the personal agent can be used.

One of the official extensions is a commerce extension co-developed with Shopify, which combines Poppy with the Universal Commerce Protocol (UCP). Poppy handles endpoint discovery and account access, while UCP handles processes such as product search, adding items to a cart and payment. With this extension, agents can shop as a guest without logging in, or log in with a customer account. However, depending on the operation, the user's permission may be required before execution.

Reflecting trial results of the draft; an implementation kit for companies is available

Personal Agent Protocol 1.0 reflects the results of about five weeks of trials of the draft by companies cooperating in drafting the specification, using actual websites, APIs and agents. The specification was arranged so that companies can start with basic support and add functions later, and the mechanisms for exchanging procedures and feedback between companies and personal agents were also expanded. For example, companies can guide agents through the order in which APIs needed for things like changing reservations should be called. Meanwhile, if a user's request cannot be handled through Poppy, the agent can report that to the company.

Regardless of whether they participated in drafting the specification, any company can make its own systems Poppy-compatible. The implementation kit for companies that supports this work includes skills that convey work procedures to coding agents and verification tools that check the implementation. The coding agent investigates existing systems according to the skills and proceeds with the design and implementation needed for Poppy compatibility. The verification tool connects to the target system as a test personal agent and can check which requirements of the specification are met.

Source

gihyo.jp