Personal Agent Consent & Trust Protocol (PACT)

PACT 1.0, open-sourced by Decagon in October 2026, builds on A2A to define how a customer’s personal agent identifies itself to a business’s support agent, and which permissions the customer has granted it.

Where it stands

As of 2026-10-13, the Agentic Standards Map records:

Version 1.0 of the specification (“This is PACT 1.0.”) is published at openpactprotocol.org (the Decagon announcement is dated 2026-10-06), and the repository openpactprotocol/openpactprotocol (created 2026-10-01, Apache-2.0) holds the documentation, a reference Provider, a demo personal agent and conformance tests; its latest commit on main is 838c6bd (2026-10-06, a dependency update), read 2026-10-13. Decagon, 2026-10-06: it is open-sourcing PACT, “co-developed and supported by Instinct”. No standards body or governing organisation is named in the pages of the site read on 2026-10-13.

Why it matters to agents

PACT builds on A2A 1.0 and defines how a personal agent identifies itself to a business’s support agent and, optionally, which permissions the customer has granted it. The business’s Agent Card is found at “https://{brandDomain}/.well-known/agent-card.json”, which “serves the card or redirects to” the Provider’s URL; the personal agent “never builds it from a Brand ID”. The Poppy protocol uses a different well-known document (see pap and seam S1). …

Sources

• https://openpactprotocol.org/spec
• https://openpactprotocol.org/
• https://github.com/openpactprotocol/openpactprotocol
• https://decagon.ai/blog/introducing-the-personal-agent-consent-trust-protocol-pact

Status and relevance quoted, shortened, from the Agentic Standards Map by Francesco Marinoni Moretto, CC BY 4.0, https://frmoretto.github.io/agentic-standards-map/. The full entry, with every dated source, is in map.json under pact.

Industry: cross-domain