---
title: "Securing Your Newest Customer Channel with Auth for Personal Agents "
description: "Auth0 brings identity to Personal Agents by adding support for the Personal Agent Protocol (Poppy). Verify agents like Muse, tie actions to real customers, and join the Beta Program."
authors:
  - name: "Karim Tantawy"
    url: "https://auth0.com/blog/authors/karim-tantawy/"
  - name: "Samantha Murphy"
    url: "https://auth0.com/blog/authors/samantha-murphy/"
date: "Nov 18, 2026"
category: "Announcements"
tags: ["ecommerce", "agents", "ai agents", "ai", "poppy"]
url: "https://auth0.com/blog/auth-for-personal-agents-beta-release/"
---

# Securing Your Newest Customer Channel with Auth for Personal Agents 

*TL;DR: Auth0 is bringing more secure identity to personal agents with support for the Personal Agent Protocol (Poppy). It helps brands across retail, travel, hospitality, and financial services let personal agents like Muse discover products, complete tasks, and transact safely on a customer's behalf, while still knowing who that customer is. Try out Poppy in our developer playground, and learn about our Auth for Personal Agents Beta Program.*

## Personal Agents are Knocking on Your Door, Are You Ready?

* **>10 million people** in the US and Canada set up Muse in just 6 weeks, making it the #1 app in the App Store almost daily.
* **>$200** is the average purchase size for shopping through Muse, its most common use case. 
* **>25%** of people who have downloaded Muse use it every day.

*Source: [Meta, 2026 (PDF)](https://s21.q4cdn.com/399680738/files/content_files/META-Q3-2026-Earnings-Call-Transcript.pdf)*  

Personal agents have exploded in popularity within weeks of launching, from Meta’s Muse to xAI’s Grok Bot. These proactive assistants remember what you’ve told them and handle everyday tasks like booking flights, finding boots, disputing charges, or getting pre-approved for a mortgage. For brands in retail, travel, hospitality, and financial services, they represent a fast-growing revenue channel, but also the one brands control least.

The problem is how these agents interact with websites. They have their own computers with browsers and impersonate the user: they collect the user’s username and password, save them, and replay them to sign in. That’s both insecure and a source of friction. Agents get full access to the account, so a brand can’t limit or trace its actions, or revoke its access without forcing a password reset. For consumers, it breaks down whenever passkeys or MFA are in place, because the agent can’t log in. And brands that block these agents, as [Amazon](https://www.inc.com/temilola-agbede/amazon-vs-walmart-ai-shopping-agent-blocking-rules-retailer-strategy/91431535) and [JPMorgan Chase](https://mashable.com/tech/chase-blocks-muse-ai-agents-banking) have done with Muse, shut themselves out of that growing channel.

More customers are using personal agents, and brands want that to happen securely. That means letting agents identify themselves, verifying the customer behind each agent, and granting only the right permissions. Brands also want to use their own identity and relationship data to personalize the experience and improve conversion, loyalty, and satisfaction. These are identity challenges to solve.

**The rest of this blog will cover:**

1. What is the Personal Agent Protocol (Poppy) 
2. Introduction to Auth for Personal Agents  
3. How it works  
4. Join our Auth for Personal Agents Beta

## What is Poppy

To help brands give these agents a better path, a new protocol has emerged: the **Personal Agent Protocol**, or **Poppy** for short. Poppy is an open protocol for how personal agents and companies work together, introduced in October by Sierra and Meta. It is built on industry standards like OAuth and JSON Web Tokens (JWTs), extending the way sign-in and permissions already work rather than reinventing them. The v1 specification is public at [personalagentprotocol.org](http://personalagentprotocol.org), and it is being shaped by a broad group of design partners spanning personal agents, companies, and technology providers, including Okta. 

To enable personal agents, Poppy is built around a few core ideas:

* **The agent identifies itself.** Each company that releases a personal agent hosts a Client ID Metadata Document (CIMD) that identifies their agent. When an agent shows up, brands can verify its metadata file to determine the agent’s identity.  
* **The customer signs in on the company's own page.** When an agent needs access to the customer’s account, the customer signs-in through the company’s standard login, and access is delegated to the agent. The agent never sees or handles any user passwords.  
* **The customer approves what the agent can do, and can revoke it anytime.** Access is scoped to exactly what the customer agrees to, not blanket account access.  
* **Pseudonymous by default.** An agent can browse or shop as a guest without handing over personal data, and only triggers sign-in when it is needed, like during a checkout.  
* **Requests are hard to fake or hijack.** Agent requests are signed and tied to that specific agent, so a stolen token or replayed request does not get very far.  
* **It works across channels.** Poppy ties together everything the same agent does for the same customer, whether that is through an API, a website, or agent-to-agent handoffs, so actions can be correlated even as the customer moves between signed-in and anonymous states.

In practice, that means in the case of shopping, an agent can build a shopping cart anonymously, then hand off to the customer to log in and approve the actual checkout, all tracked as one continuous, trusted interaction rather than a handoff into the dark. 

### Test your shop with our Poppy developer playground

To learn about how Poppy works you do not need to read the full spec to find out. We developed a developer playground for Poppy ([poppyplayground.dev](https://poppyplayground.dev/)) as a free, educational, browser-based tool that gives your shop a test drive, see what the agent sees, its computer and the browser it drives. Try it out against sample sites or other existing sites; and then as you build support for it you can test your implementation out here too. Enter your shop's web address, and the playground verifies your site’s metadata and runs a personal agent you can interact with against your site, running through the same steps a real one would take:

* Discovery: Can the agent find your shop and learn what it supports?  
* Sign-in: Can the agent connect securely on a customer's behalf?  
* Using the shop: Can the agent browse products or look up an order?  
* Conversation: Can the agent hold a natural back-and-forth with your shop?  

At each step, this developer playground shows you exactly what was sent and received, so if something does not work, you can see where and why. It is a simple way to see your Poppy implementation through an agent's eyes before a real one shows up.

![The Poppy developer playground shows a personal agent building a cart on the fictional Tarn & Timber shop while prompting the user on mobile to sign in and grant scoped checkout permissions.](https://images.ctfassets.net/23aumh6u8s0i/7uO2WZRKkTLDnVoZ4S20As/695cf25661afe043869bff963e6cd7c0/poppy-screenshot.png)

## Introduction to Auth for Personal Agents

Auth0 is one of the first identity providers to support Poppy with support for the Personal Agent Protocol Solution, available soon in Beta. We provide the identity and trust layer that lets personal agents act on a customer's behalf safely, so brands can confidently open the door to agent-driven interactions without taking on unnecessary risk or a full replatforming project. With Auth for Personal Agents, brands can recognize which agent is knocking at their door by allowing them to identify themselves through CIMD, tie every action back to a verified human customer, and enforce granular, time-bound permissions, such as allowing an agent to browse and build a cart pseudonymously before stepping up to human authentication at checkout.

Why this matters to you:

* If you own the **revenue** number: Personal agents are becoming a real traffic source. Auth for Personal Agents lets you say yes to that traffic so you can convert and grow trusted customer interactions instead of blocking them out of caution.
* If you are responsible for **security**: Every agent action carries a verifiable identity and a scoped, revocable grant: no standing credentials and no guessing who or what touched an account.
* If you are a **builder**: Agents can browse your existing website on the customer's behalf, not just call your API, with minimal changes on your end. We handle the protocol endpoints and SDK work. We also handle the agent authentication and consent flows, so you are not stuck reverse-engineering trust for every new agent that shows up at your door.

## How It Works

The Beta will support both API access and web browsing, letting an agent navigate your existing web app directly, not just call an API. Each surface works signed-out (anonymous) or signed-in. Signed-in interactions use a redirect-based sign-in, so the agent never sees or handles the user's password.

Here is how it works:

* **Discovery, handled for you.** Our web app SDK serves `/.well-known/poppy.json` and the protected resource metadata, driven by a configuration file generated for your tenant.  
* **Choose which agents you allow.** You register each personal agent you want to support from its CIMD URL and link it to an agent principal in Auth0. Registration is your allow list, and you can block any agent later.  
* **Direct sign-in and consent.** Users sign-in through standard OAuth flows with a consent screen showing the agent's name and logo. Agents refresh and revoke tokens the standard way.  
* **DPoP-bound tokens.** Access and refresh tokens issued to agents are bound to the agent's key.  
* **Agent identity in your tokens.** Your APIs can see both the user and the agent acting for them, so you can log, limit, and audit agent activity separately from human activity.  
* **Verification for your APIs and web app.** New SDK support checks the `Poppy-Session` header and token binding on your APIs, and handles agent-driven sessions on your web app, including guests who have not signed in yet.  
* **Helpful CLI commands to set it up.** New Auth0 CLI commands to set up Poppy on your tenant, register or block an agent, and run a `doctor` check on your discovery chain allowing you to get up and running in minutes.

<include src="Vidyard" id="DhhTCY5ryNsft4uF3UP2zV" />

Here is how a typical interaction flows:

1. The agent fetches your `poppy.json` and OAuth metadata and confirms the issuer matches.  
2. The agent calls your API as a signed-out Session and can already do whatever you allow anonymously.  
3. When it needs account access, it sends the user through sign-in and consent on your Auth0 tenant.  
4. The agent gets DPoP-bound tokens, and each request carries the Session header and token, which your API verifies.  
5. If the agent needs your website, it joins its browser to the Session and lands in a normal login on your web app, as a guest or as the signed-in user.

![Poppy developer playground typical interaction flow](https://images.ctfassets.net/23aumh6u8s0i/1sxKIFdQmzeBoHoz499dXb/3d1185b8c9b9e6f917caf07b9e3297a5/Auth_for_Personal_Agents_Flow.png)

## Join the Auth for Personal Agents Beta Program Coming Soon

Auth0 is opening a Beta Program for teams who want to get ahead of personal agents showing up at their front door: identity and platform teams in retail, travel, hospitality, financial services, and any company whose customers will soon send agents to act for them.

If selected for the Beta Program, you will be able to spin up an Auth0 test tenant to see how simple implementation is helping secure personal agents with Auth0. You can also use our Poppy developer playground to see how discovery, sign-in, and token binding actually work with your implementation.

If you are evaluating how to support personal agents, let’s talk.

Sign up to express interest in [Auth0's Auth for Personal Agents Beta Program here](https://docs.google.com/forms/d/e/1FAIpQLSdAlLggUc1YJXpMda33X3XMuBsuSFmq0-BYU-jE6T7RuGDnFA/viewform?usp=header)

## Learn More

* Try out Poppy in our [developer playground](https://poppyplayground.dev/).  
* Read [Securing the Front Door of Agentic Commerce](https://auth0.com/blog/securing-the-front-door-of-agentic-commerce/) for more on the identity requirements of agent-driven channels.  
* Read our [Auth for UCP blog](https://auth0.com/blog/securing-agentic-commerce-using-auth0-universal-commerce-protocol-ucp/) to understand how we are supporting a parallel agent-driven channel.  
* Check out the Poppy specification and docs at [personalagentprotocol.org](http://personalagentprotocol.org).  
* If you do not have an Auth0 account yet, [create one for free](https://a0.to/blog_signup).
