What Poppy enables
Poppy describes how a personal agent works with a business on its user's behalf. It covers discovering interfaces, sessions, signing in to a customer account and accessing business functions. This lets an assistant support a customer relationship across individual requests.
Connections with other protocols
- Poppy connects a personal agent with a business and the user's customer account. An integration can use UCP for the purchase itself.
- The Operations extension describes additional business functions within Poppy.
- PACT also addresses personal agent identity and delegated account access, building on A2A.
Versions and licence
- Published version
- 0.1 (published draft) ·
- Working draft
- 0.2
0.1 is frozen at its own URL. Draft 0.2 is not yet published and includes changes marked as breaking.
- Licence / terms
- Apache-2.0 for the specification and documentation; trademarks, logos and design are excluded. Datalayer community SDKs: BSD-3-Clause.
Licence and terms ↗
An example flow
- A personal agent discovers a business's published interfaces.
- It starts a session. The user signs in to the business for account related functions.
- The agent uses an offered function, such as checking an order status on the customer's behalf.
- The session keeps subsequent requests within the same customer context.
SDKs and examples
These libraries and examples help you get started. Each entry lists the language, package and supported version.
Official Company Kit
Includes: Specification, Company Kit and validator tests
Package / module: kit/company in the repository
Version & compatibility: Company Kit and validators for the specification
Templates and validators for business integration in the official repository.
Datalayer Personal Agent Protocol
Includes: Community SDKs
Package / module: personal-agent-protocol; @datalayer/personal-agent-protocol
Version & compatibility: Python 0.26.0 on PyPI (22 October 2026); TypeScript 0.26.0 in the repository. Targets draft 0.2 dated 18 October 2026 and Operations v1.
The application persists tokens and previously used requests. For metadata retrieval in Node, the project recommends an egress proxy because socket pinning is absent.
Practical integration
- Published draft 0.1 has its own versioned address. The current specification page shows draft 0.2 with changes to the flow.
- The Company Kit includes templates and validators for connecting business interfaces.