Descope Envoy separates an agent’s access from its user’s session
Descope has introduced Envoy so consumer applications can recognize personal AI agents separately from the people they represent. Businesses can limit permissions by action and revoke an agent’s access while keeping the customer signed in. The service supports the Personal Agent Protocol draft and offers a separate approval channel for sensitive transactions.
Artificial Intelligence··Evening
Agents get their own identity
Descope, a company providing identity-management software, introduced Envoy on 4 November for consumer websites and applications accepting personal AI agents. The software acting for a customer receives a separate identity, alongside the application’s existing customer sign-in system. Agent access can be withdrawn while the person stays signed in. Session tokens and transaction logs distinguish the customer from the software representing them.[1], [2]
Businesses restrict individual actions
Envoy supports the Personal Agent Protocol draft published by Meta and Sierra in October. Also known as Poppy, it lets businesses advertise endpoints for agents and authenticate connecting software. Session tokens are bound to the agent’s key. Permissions can allow a shopping agent to inspect products and place orders while withholding changes to account settings or payment methods. Businesses determine how long elevated access lasts.[1]
Sensitive purchases use a separate approval channel
Descope describes approval outside the agent’s session for sensitive actions. In its flight-shopping example, the customer receives the airline, times and total amount on their phone before authorizing the transaction. The company also released a TypeScript software development kit for Poppy. It handles endpoint discovery, client metadata, session management and calls bound to the agent’s key, supporting developers connecting their agents to consumer applications.[1]