Eyebrow Text
BLOG
Title
Ping Identity Named Personal Agent Protocol Design Partner
Subtitle
The protocol covers how personal agents and organizations discover one another, establish user-authorized access, and interact
title
Table of Contents
theme
default
centered
false
heading
Key Takeaways
body
  • The Announcement: Ping Identity is a Design Partner for the Personal Agent Protocol (Poppy), an open standard co-developed by Sierra and Meta.
  • Who It Helps: Organizations working with personal AI agents get help choosing interaction models and keeping account holders in control of sensitive actions.
  • Why It Matters Now: Personal AI agents are taking on more tasks for people, so organizations need interactions that are useful, trusted, and accountable.

As personal AI agents take on more tasks for people, a central question is how they can interact with organizations in ways that are useful, trusted and accountable. The answer must make room for innovation while keeping people in control of their accounts and protecting organizations from malicious activity.

Ping Identity is proud to be a Design Partner for the Personal Agent Protocol (Poppy), an open standard co-developed by Sierra and Meta. Poppy covers how personal agents and organizations discover one another, establish user-authorized access, and interact, including payments through its UCP extension. DPC, AP2, and Verifiable Intent standards add complementary layers for payment authentication and for proving user intent.

Ping is committed to helping cooperative, market-leading personal AI agents interact responsibly, safely and securely with organizations; while simultaneously helping protect account holders and organizations from adversarial and criminal AI activity. We're pleased to bring our identity and access management perspective to the standard's evolution.

How Poppy Supports APIs, Websites, and Company Agents

Poppy describes multiple ways an agent can work with a company: through its APIs, by browsing its website, or in a conversation with the company's own agent. Supporting this range matters. Organizations should be able to choose the interaction model that fits each service and task, while applying clear identity, authorization and accountability across them.

As customers explore Poppy, Ping's goal is to help support these different methods of interaction and make adoption practical. That includes helping customers understand the standard, educating teams on its implications, and working through use cases and implementation considerations with them as Ping enables support. Our participation as a Design Partner is an opportunity to share customer needs with the Poppy community early.

Human-in-the-Loop Approval for Sensitive Agent Actions

Not every action carries the same risk. A request to check a status may need a different level of assurance than changing account details or approving a payment. For sensitive or consequential transactions, a human-in-the-loop confirmation can provide an important safeguard: the account holder reviews and approves the specific action before it proceeds.

The confirmation method should match the risk and context. Organizations can use risk-based adaptive access (PingOne Protect) to determine when additional checks are needed, then confirm the person's identity through traditional MFA or FIDO passkeys, or privacy-preserving biometric matching (PingOne Recognize).

For sensitive transactions, portable digital credentials in a secure wallet with messaging (PingOne Neo) combines identity confirmation and approval of the specific action in one interaction. Approval happens through a separate, end-to-end encrypted channel on the person's approved device, tying their identity, account, and organization to the transaction. This helps protect against unauthorized or malicious AI activity and creates a tamper-evident, independently verifiable record of exactly what the person approved.

Another important design consideration is how an agent is linked to the human behind it, the account holder and any other people authorized to act on the account. Depending on the use case, that binding or delegation could be centralized or decentralized, and could reflect progressive identity-proofing levels of assurance (PingOne Verify).

Flexibly and dynamically combining these approaches using identity orchestration (PingOne DaVinci) gives organizations room to match assurance to risk, privacy and customer experience requirements.

Poppy doesn't require any specific vendor. Here is how Ping customers can approach this.

How Agentic Commerce Standards Fit with Personal Agents

Ping is also a member of the FIDO Alliance Payments Technical Working Group and is helping create the complementary Digital Payment Credential (DPC) in partnership with EMVCo, as well as the next version of the AP2 and Verifiable Intent standards including for use in agentic commerce. This work complements Poppy rather than competing with it.

The FIDO Alliance's work delivers two additional, complementary layers: Poppy focuses on how personal agents discover and interact with organizations and obtain user-authorized access, while DPC establishes a step-up combined authentication and authorization pattern that can be bound to a particular payment method, and AP2 and Verifiable Intent define how user intent is created and shared, and how it is proven in an agentic AI interaction. Together, these distinct efforts can contribute to a more interoperable trust model across agentic transactions and commerce.

Extending Personal Agent Access with Identity for AI

Customers may also choose to use capabilities from Ping's Identity for AI suite alongside their Poppy adoption plans. The suite includes agent detection and discovery, agent lifecycle and management, runtime authentication and authorization, and agent mediation capabilities for APIs and MCP access. These capabilities can complement a standards-based approach by helping organizations understand which agents are active and govern what they can do at runtime.

How Ping Supports Both Poppy and Non-Poppy Personal Agents

Ping recognizes that not all personal AI agents will support the new Poppy protocol or be built in a way that can accommodate it. Ping continues to work with our customers and agentic ecosystem providers to consider how to support interactions with non-Poppy agents while applying appropriate controls, as well as address other types of AI agents.

However, the Poppy 1.0 milestone is an important opportunity to bring the ecosystem together around more consistent agent-to-business interactions. As a Design Partner, Ping looks forward to collaborating with the Poppy community and our customers to help shape an open standard that supports innovation without losing sight of identity, authorization, security and human agency.

Further Reading

Frequently Asked Questions

What is the Personal Agent Protocol?
The Personal Agent Protocol (Poppy) is an open standard co-developed by Sierra and Meta. It covers how personal agents and organizations discover one another, establish user-authorized access, and interact, including payments through its UCP extension. DPC, AP2, and Verifiable Intent add complementary layers for payment authentication and for proving user intent.
What is Ping Identity's role in the Personal Agent Protocol?
Ping Identity is a Design Partner for Poppy. Ping brings its identity and access management perspective to the standard and shares customer needs with the Poppy community early.
How does Ping help keep people in control of sensitive agent actions?
Ping helps keep people in control of sensitive agent actions by matching the confirmation method to risk and context. PingOne Protect determines when additional checks are needed, and PingOne MFA, PingOne Recognize, or PingOne Neo confirm identity or approval. PingOne DaVinci orchestration combines these approaches.
How does Poppy relate to DPC, AP2, and Verifiable Intent?
Poppy relates to DPC, AP2, and Verifiable Intent as a complementary layer of trust. Poppy covers how personal agents discover organizations and obtain user-authorized access. DPC adds a step-up authentication and authorization pattern bound to a payment method, while AP2 and Verifiable Intent define how user intent is created, shared, and proven.
title
Dive into the Details of Poppy
body
See how Ping is working with the Poppy to support responsible AI agent interactions.
Supporting text
primary-link
https://personalagentprotocol.org/
primary-link-text
Explore the Personal Agent Protocol
primary-link-title
Explore the Personal Agent Protocol
use-tertiary-arrow-button-style
secondary-link
secondary-link-text
secondary-link-title
use-tertiary-arrow-button-style-2