Your AI assistant can already find the perfect snowboard, compare prices across a dozen stores, and pick the right size. The moment it tries to actually buy it for you, everything breaks. The store has no idea who the assistant is, whether you really asked it to spend your money, or what it is allowed to do on your account.
On November 4, 2026, Descope launched Descope Envoy to fix exactly that gap: a way for your personal AI agent to sign in to a website as itself, with its own identity, its own permissions, and your approval — instead of borrowing your password and pretending to be you. This guide explains what Descope Envoy is, how it works, what it does not do yet, and why it matters for anyone who shops, banks, or books with an AI assistant.

Table of Contents
- What Is Descope Envoy?
- The Problem Descope Envoy Solves
- How Descope Envoy Works, Step by Step
- The Personal Agent Protocol (Poppy) Behind Descope Envoy
- Descope Envoy vs the Alternatives
- Who Is Descope Envoy For?
- What Descope Envoy Does Not Do Yet
- What Descope Envoy Means for Shoppers
- How to Get Started With Descope Envoy
- Frequently Asked Questions
- The Verdict: Should You Care About Descope Envoy?
What Is Descope Envoy?
Descope Envoy is a set of identity capabilities that lets a consumer website or app give a personal AI agent a secure, delegated sign-in path — a dedicated lane for agents that runs alongside the normal human login flow.
It was announced on November 4, 2026, by Descope, a developer-friendly customer identity platform based in Los Altos, California. Instead of an agent logging in with your username, your password, and your one-time code, Descope Envoy lets the business recognise the agent as a separate actor: it verifies who the agent is, who it is acting for, and exactly what it is allowed to do, and it keeps the customer and the agent distinct in every token and log entry.
The simplest way to think about Descope Envoy is as a guest pass with rules attached. A human customer signs in the way they always have, and nothing about their experience changes.
When their AI assistant arrives — to buy a snowboard, reorder a prescription, or donate to a fundraiser — it gets its own pass. That pass says who the agent is, which customer sent it, and which actions it may perform. The store can revoke the pass at any time without touching the customer’s own account, and every action the agent takes is logged under the agent’s name, not the customer’s.
Descope Envoy is built on the Personal Agent Protocol, known as Poppy, a draft standard published by Meta and Sierra in October 2026. Envoy gives consumer-site developers an abstraction layer: they can become Poppy-compliant and welcome agents without implementing the protocol themselves or tracking every change as the specification evolves. Descope also published a Poppy JavaScript SDK so agent builders can connect to any Poppy-supporting company in a few lines of TypeScript.
Launch and design partners working with Descope on Envoy include GoFundMe, GoodRx, Linktree, You.com, Elementor, and Composio. That list matters because it shows the first wave of real consumer services — fundraising, pharmacy, link pages, search, website building, and agent tooling — that are preparing to accept personal agents as first-class users rather than blocking them at the door.
The Problem Descope Envoy Solves
Every login page, consent screen, and session on a consumer website was designed on one assumption: a person is on the other side. That assumption is breaking fast. Personal agents such as Meta’s Muse and Spear Street’s Instinct now handle the full end-to-end shopping story for their users: search for a product, pick the right size, and place the order. When one of those agents arrives at a store’s website, the store faces three bad options, and Descope’s launch blog lays them out plainly.

Option one: block the agent. The store keeps its site clean and its data safe, but it loses the sale — and the customer who sent the agent. Blocking is already happening at scale: Amazon blocked Meta’s Muse from its store in September 2026, saying the agent did not identify itself as one when placing orders. Our earlier coverage of why websites block AI agents showed Yelp, Delta, JPMorgan Chase, and Charles Schwab taking the same route for different reasons. Blocking works, but it turns away revenue.
Option two: let the agent scrape and impersonate. The agent signs in with the customer’s own password and one-time code, and the site cannot tell the agent apart from the person. The business loses all visibility into who is acting, on whose behalf, and with what permissions. Worse, an agent misusing that access can drive up product returns and support overhead, because nothing limits what it can touch once it is inside the account. This is the path most agents are forced down today, and it is the least safe option for everyone involved.
Option three: rebuild the entire identity stack. The business could rebuild its customer identity and access management system to support agents natively — a project that takes quarters of engineering work while agentic commerce is already exploding. Few consumer companies can afford that delay, and fewer still want to maintain a second identity system forever.
Descope Envoy is designed as a fourth option: accept the agent, but on your terms, without rebuilding anything. It sits alongside the existing sign-in flow, so humans keep the experience they have today, and agents get a dedicated lane with their own identity, approvals, and limits. Descope’s position, stated when it shipped its Agentic Identity Hub 3.0, is that banning agents outright is not a feasible option for businesses that want the benefits of AI — so the practical question is how to let them in safely.
That framing connects directly to the wider shift we have been tracking on this site. Walmart’s Agent Gateway, covered in our Walmart AI shopping agents guide, lets assistants search and buy at Walmart and Sam’s Club — but a gateway only works if the store can tell a legitimate agent from a scraper. Descope Envoy supplies the identity layer that makes that distinction possible.
How Descope Envoy Works, Step by Step
Descope Envoy runs alongside your existing sign-in, whether or not your customer identity system runs on Descope. The flow has three stages, and each one solves a different part of the impersonation problem. Here is how a purchase works when a site has Envoy in place.
Step 1: The agent arrives and proves who it is
A shopper tells their assistant, “I want to buy a new snowboard.” The agent finds a suitable store, browses the catalogue, confirms the sizing, and gets ready to place the order.
At that point, instead of typing in the customer’s password, the agent presents itself through the Personal Agent Protocol. Envoy verifies the agent’s identity and the customer it is acting for. Agents need no advance registration with the store, because each one presents a published client metadata document that Envoy can check on the spot. The session token issued to the agent is cryptographically bound to a key the agent holds, using Demonstrated Proof of Possession (DPoP), so a stolen token alone is useless to anyone else.

Step 2: You approve exactly what the agent does
Before anything happens on the customer’s account, Envoy sends the user an approval request describing the exact action: the item, the size, and the total. Nothing happens on a customer’s behalf until they have seen and approved it. The approval request appears natively wherever the customer uses their personal agent — in messaging apps such as iMessage and WhatsApp, or in the agent’s own dedicated app. This is called out-of-band approval, and it is the single most important safety feature in the design: the person who pays is always in the loop, on a device and channel they already trust, even though the agent is doing the work.
Companies can fully customise the approval journey and the granularity of the permissions an agent requests, using Descope Flows. A store might ask for approval on every purchase above $25, but let the agent reorder household basics under that amount without bothering the customer. The business sets the rules; the customer sees and approves the specific action.

Step 3: Your policies set the limits
The business decides what agents are allowed to do on its site. A personal shopping agent might be able to read catalogue items and place and edit orders — and nothing else. No account settings, no payment method changes, no access that was not granted. The permissions are expressed with Rich Authorization Requests (RAR), a standard way to describe exactly which resources and actions a token may touch, so the limits are enforced by the system rather than trusted to the agent’s good behaviour.
The duration of an agent’s elevated access is also fully customisable. A store can give an agent a session that lasts for one checkout, one afternoon, or one recurring order — and then it expires. Through identity federation, businesses can also layer their existing customer identity requirements on top of Envoy, including multi-factor authentication (MFA). The result is that an agent’s access is narrower, shorter-lived, and more visible than a human password ever was.
The Personal Agent Protocol (Poppy) Behind Descope Envoy
To understand why Descope Envoy exists, you need to understand Poppy. The Personal Agent Protocol is a draft standard — version 0.1 — published by Meta and Sierra in October 2026. It answers a question the web has never had to answer before: how does a website know that the visitor placing an order is an AI agent acting for a real customer, and not a bot, a scraper, or a fraudster?
Poppy gives businesses a way to publish what their agent-facing endpoints are, verify the identity of the agent making the request, and issue a session that is cryptographically bound to that agent for the length of the interaction. It covers three sign-in types, and Envoy supports all three. The key design choice is that the agent is identified as an agent: it presents a client metadata document, the business verifies it, and the resulting session token is tied to the agent’s own cryptographic key. Nobody has to pre-register the agent, and nobody has to hand the agent a human’s credentials.
Envoy’s role is to make Poppy usable without deep protocol work. Implementing a draft specification that is still changing is exactly the kind of project that stalls inside a consumer company: the spec will keep evolving, the edge cases are endless, and the security stakes are high. Descope handles discovery, agent identification, DPoP-bound tokens, and all three sign-in types, and it keeps the implementation current as Poppy changes. The business gets a Poppy-compliant front door for agents while its human sign-in flow stays exactly as it is.
Descope is also supporting the other side of the ecosystem. Alongside Envoy, it published a Poppy JavaScript SDK for AI agent builders.
With the SDK, a personal agent can connect to any company that supports Poppy in a few lines of TypeScript: point it at a website, and it discovers the company, opens a session for the user, signs them in with device sign-in, and calls the company’s APIs with DPoP-bound tokens that it renews and revokes on the builder’s behalf. The SDK has no external dependencies, according to coverage of the launch, which keeps it light enough to drop into an existing agent.

Poppy is still a young standard, and Descope is open about that: the specification will keep changing, and Descope plans to maintain the SDK as new versions are adopted. That honesty matters. A business adopting Envoy today is betting on a protocol at version 0.1, not on a finished, frozen standard. The bet is reasonable — Meta and Sierra are serious backers, and the problem Poppy solves is not going away — but it is a bet, and any honest guide should say so.
Descope Envoy vs the Alternatives
Descope Envoy is not the only attempt to make agentic commerce safe. Several different layers of the problem are being solved at once, and Envoy sits at the identity layer. Here is how it compares with the approaches a business or a shopper is most likely to meet.
| Approach | How it works | Strength | Weakness |
|---|---|---|---|
| Block agents entirely | Detect and refuse agent traffic at the door | Simple, safe, no new code | Loses sales and customers who shop by agent |
| Let agents impersonate users | Agent logs in with the customer’s password and one-time code | Works today, no changes needed | No visibility, no limits, no revocation without locking the customer out |
| Descope Envoy | Agent gets its own identity, scoped permissions, and out-of-band approval | Safe, visible, revocable, no rebuild of the identity stack | Depends on the young Poppy draft standard; no general-availability date yet |
| Payment-layer controls | Agent payment systems such as Mastercard Agent Pay tokenise and limit transactions | Protects the money at the moment of payment | Does not identify the agent or control what it can see and do on the account |
| Credential vaults for agents | Tools such as 1Password for Agents issue scoped credentials to agent workloads | Strong secrets hygiene for developer-built agents | Built for internal agent workloads, not for a shopper’s personal assistant on a consumer site |
The honest reading is that these approaches complement each other rather than compete. Mastercard Agent Pay, which we covered in our Mastercard Agent Pay guide, protects the payment itself: it tokenises the card and sets spending rules for agent transactions.
Descope Envoy protects everything before the payment: who the agent is, what it can see, and whether the customer approved the action. A store that wants agents to buy safely will eventually want both — identity at the front door and payment controls at the checkout. Similarly, 1Password for Agents, covered in our 1Password for Agents guide, solves credential hygiene for agents a company builds and runs itself; Envoy solves identity for agents a customer brings with them. Different agents, different doors, same underlying problem.
The comparison that matters most for a consumer business is the simplest one: blocking versus Envoy. Blocking costs nothing to implement and costs revenue every day it runs. Envoy costs integration effort and asks the business to trust a new protocol, but it keeps the revenue and adds visibility the business never had — a separate log of everything agents did, under the agent’s own name. For a retailer watching agentic shopping grow, that trade is the whole pitch.
Who Is Descope Envoy For?
Descope Envoy is aimed at two audiences, and the launch is built for both. The first is consumer businesses: retailers, pharmacies, fundraising platforms, and any company whose customers now arrive with an AI assistant in tow. For them, Envoy is a way to say yes to agent traffic without a quarters-long identity rebuild. The launch partners sketch the first wave: GoFundMe (donations made by an agent on a supporter’s behalf), GoodRx (prescription orders and refills), Linktree and Elementor (creators and small businesses whose customers increasingly shop through assistants), You.com (search-led shopping), and Composio (agent tooling that connects agents to apps).

The second audience is agent builders. If you are building a personal agent, Envoy and the Poppy SDK give you a legitimate front door instead of the current workaround of borrowing the user’s password. That matters more than it sounds: an agent that logs in as the user can be flagged as a bot, locked out by fraud systems, or blamed for actions it never took. An agent that arrives through Poppy is recognised, expected, and logged as itself. For builders, that is the difference between a product that works until a site notices it and a product that is welcome.
Envoy also builds on Descope’s Agentic Identity Hub, which already handles authentication and access control for more than 1,000 MCP servers and millions of monthly agentic transactions. That scale claim, from Descope’s own announcement, is worth noting because it answers the obvious question: has this company handled agent traffic before, or is Envoy a first experiment? The answer is that the underlying hub is already running at volume for developer-facing agent workloads; Envoy extends the same identity thinking to consumer-facing personal agents.
Who should not rush in? Small businesses that do not see agent traffic yet, and companies in regulated industries that need their compliance teams to review any new authentication path first, should watch the launch partners’ results before committing. Envoy is new, the protocol is a draft, and there is no general-availability date — early adoption is for teams that already feel the agent traffic and want a controlled way to accept it.
What Descope Envoy Does Not Do Yet
Every honest guide to a new launch needs a limits section, and Descope Envoy has several that matter. First, there is no general-availability date. The announcement describes launch and design partners who will work alongside Descope to improve Envoy in the months to come — which means the product is live enough to start with, but still being refined with real partners. If you are evaluating it for a production rollout, expect a design-partner conversation rather than a self-serve switch you flip today.
Second, Poppy itself is a draft. Version 0.1 was published in October 2026, and the specification will keep changing. Descope has committed to maintaining its SDK as the protocol evolves, but any business building on Envoy is building on a moving standard. That is normal for new web protocols — OAuth and WebAuthn both went through the same phase — but it means integration work done today may need updating as Poppy matures.
Third, Descope has not announced pricing for Envoy. The announcement and the launch blog say nothing about what it costs, whether there is a free tier, or how it is metered. Do not assume it is free, and do not budget on a number you read in a summary — check Descope’s pricing page or talk to the company before planning a rollout.
Fourth, Envoy does not solve the whole agentic-commerce problem by itself. It identifies the agent and controls what the agent can do, but it does not verify that the agent’s recommendation is good, that the product is in stock, or that the price is fair. It does not replace payment controls, fraud detection, or returns policies. Think of it as the front door with a guest list — necessary, but not the whole store.
Finally, adoption is the open question. Envoy only helps where businesses install it. An agent that arrives at a site without Envoy still faces the old three bad options. The launch partners are a promising start, but the value of the system grows with every store that joins. Until Poppy support is widespread, agents will keep hitting closed doors — which is why the partner list, not the feature list, is the number to watch over the next few months.
What Descope Envoy Means for Shoppers
For the person on the other side of the screen — the shopper who told their assistant to buy the snowboard — Descope Envoy changes the experience in ways that are mostly invisible, and that is the point. You will not see a new login screen. You will not create a new account. What changes is what happens behind the scenes when your agent acts for you.
Today, when your agent buys something, it usually does so with your password. That means it can see everything you can see: your saved payment methods, your order history, your account settings, your address book. If the agent makes a mistake, or if its session is hijacked, the blast radius is your whole account. With Descope Envoy in place, the agent sees only what the store allowed it to see, does only what you approved, and loses access the moment the task is done or you revoke it. Your password never leaves your hands.
The approval step is the part shoppers will actually notice, and it is designed to feel familiar: a message on your phone, in iMessage or WhatsApp, showing the item, the size, and the total, with an approve button. It is the same pattern as approving a bank transaction on your phone, applied to agent shopping. The first few times it may feel like an extra step; after that, it becomes the reason you trust the agent with bigger purchases. Trust, in agentic commerce, is not built by removing friction — it is built by showing the customer the exact action before the money moves.
There is a longer-term payoff too. Right now, the safest advice for anyone using a shopping agent is to keep a separate card with a low limit, watch every order, and expect some stores to block the agent outright. As identity layers like Descope Envoy spread, that advice gets simpler: the agent arrives as itself, the store knows it, you approve the purchase, and the receipt shows the agent’s name next to yours. The shopping agent stops being a clever hack around the login page and becomes a normal, recognised way to buy things.
How to Get Started With Descope Envoy
If you run a consumer website or app, the starting point is Descope’s Envoy page and documentation, linked from the company’s official Envoy announcement. Descope offers a sign-up path and a demo with its agent and human authentication experts, and the documentation covers how Envoy sits alongside an existing identity system — including systems that do not run on Descope at all. Because Envoy is being refined with launch partners, expect an onboarding conversation rather than a purely self-serve setup, and ask directly about availability timelines and pricing before you commit engineering time.
If you build personal agents, the starting point is the Poppy JavaScript SDK on GitHub, which Descope published alongside Envoy. The SDK lets your agent discover Poppy-supporting companies, open a session for the user, sign them in with device sign-in, and call company APIs with DPoP-bound tokens it renews and revokes for you. Since Poppy is still a draft, build against the SDK rather than implementing the protocol by hand — Descope has said it will maintain the SDK as the specification changes, which saves you from tracking every revision yourself.
If you are a shopper, there is nothing to install. Envoy is infrastructure that businesses adopt, not an app you download. The practical step is to watch for it: when a store you use announces support for personal agents or for the Personal Agent Protocol, that is Envoy-style identity arriving at a place you shop. Until then, keep doing what careful agent shoppers already do — approve each purchase, check the order confirmation, and never hand your main password to an agent that asks for it.
For developers evaluating the space more broadly, Envoy pairs naturally with the latency work happening on the agent side. Our Claude Message Threads guide explains how Anthropic cut the wait on very long agent sessions by about 35% — faster agents plus identified agents is the combination that makes an AI assistant feel less like a demo and more like a reliable employee.
Frequently Asked Questions
What is Descope Envoy?
Descope Envoy is a set of identity capabilities, announced November 4, 2026, that gives personal AI agents a secure, delegated sign-in path to consumer websites and apps. It lets a business recognise an agent as a separate actor with its own identity, permissions, and approval flows, instead of the agent logging in with the customer’s password.
Is Descope Envoy free?
Descope has not announced pricing for Envoy. The launch announcement and blog do not mention a price, a free tier, or metering. Check Descope’s pricing page or contact the company for current pricing before planning a rollout.
What is the Personal Agent Protocol (Poppy)?
Poppy is a draft standard, version 0.1, published by Meta and Sierra in October 2026. It lets businesses publish their agent-facing endpoints, verify an agent’s identity, and issue a session cryptographically bound to that agent. Descope Envoy implements Poppy so businesses do not have to build it themselves.
How is Descope Envoy different from just giving my agent my password?
With your password, an agent can do everything you can do, with no limits and no separate log of its actions. With Descope Envoy, the agent gets its own identity, only the permissions the business granted, out-of-band approval from you for each action, and a session that expires. The business can revoke the agent’s access without touching your account.
Which companies are using Descope Envoy?
Launch and design partners named by Descope include GoFundMe, GoodRx, Linktree, You.com, Elementor, and Composio. They are working with Descope to refine Envoy over the coming months, so expect wider availability to follow rather than arrive all at once.
Does Descope Envoy work with my existing login system?
Yes. Envoy runs alongside your existing sign-in, whether or not your customer identity system runs on Descope. Humans keep the experience they have today, and agents get a dedicated lane. Through identity federation, businesses can also apply existing requirements such as multi-factor authentication on top of Envoy.
Can an AI agent buy things without my approval through Descope Envoy?
No. Nothing happens on a customer’s behalf until they have seen and approved the exact action — the item, the size, and the total. The approval request arrives out of band, in messaging apps such as iMessage and WhatsApp or in the agent’s own app, and the business can customise how granular those approvals are.
The Verdict: Should You Care About Descope Envoy?
Descope Envoy is not a product most readers will ever touch directly, and that is exactly why it matters. The agentic web is arriving faster than the web’s identity systems can handle it: agents are already shopping, booking, and ordering on behalf of real people, while the login page still assumes a human is typing.
The choice facing every consumer business is no longer whether agents will come — it is whether to block them, let them impersonate customers, or give them a legitimate front door. Envoy is the most concrete version of that third option yet, built on a real draft standard, with real launch partners, and with the safety properties that matter most: the agent is identified, the permissions are scoped, the customer approves, and the access expires.
It is early. Poppy is at version 0.1, there is no general-availability date, pricing is unannounced, and adoption will decide whether this becomes infrastructure or a footnote.
But the direction is unmistakable, and it matches everything else happening in the space: Walmart opening its doors to agents, Mastercard tokenising agent payments, Anthropic making long agent sessions faster. The agent economy needs an identity layer the way the human web needed passwords and, later, passkeys. Descope Envoy is a serious attempt to build it — and if you shop with an AI assistant, or run a store its customers shop at, it is worth watching closely over the next few months.
Sources: Descope’s official Envoy announcement (descope.com) and the company’s November 4, 2026 press release via GlobeNewswire; additional reporting from SiliconANGLE and TokenPost. All performance and scale figures are the companies’ own claims unless stated otherwise.
