Open standard
for verifiable interaction records
PEAC is the open standard for verifiable interaction records. Originary is one product built on top of it. PEAC defines how systems publish machine-readable interaction terms and issue signed records for automated requests. Verify them independently, even offline.
Originary is one implementation. PEAC remains open, neutral, and implementation-independent.
What PEAC defines
Three protocol surfaces for verifiable automated interactions
Policy discovery
Publish machine-readable interaction terms and rules at a well-known endpoint. Agents and systems discover your policies before making requests.
Interaction record format
Issue signed records for automated requests. Ed25519 signatures, compact JWS serialization, and deterministic claim structure.
Verification and conformance
Verify records independently with the public key alone. Conformance testing ensures cross-implementation compatibility deterministically.
What PEAC does not replace
PEAC is designed to interoperate with adjacent standards rather than replace them.
Implementation status
PEAC is an open standard under active development. No single implementation has privileged status. Originary is one implementation; independent implementations are welcome. Conformance testing is the interoperability anchor.
Ten verification domains
Protocol capability map for verifiable automated interactions
Who and why
Access
Declare who can use your resources and under what conditions
Identity
Cryptographic proof-of-control for agents and operators
Purpose
Declared intent of each interaction and purpose-driven access
Trust and governance
Consent
Explicit, machine-readable consent before access
Privacy
Minimal disclosure and selective transparency
Compliance
Audit trails and records for regulatory requirements
Safety
Defense-in-depth security and safe-by-default configuration
Evidence and value
Attribution
Every request carries verifiable identity and intent
Provenance
Cryptographic proof of what happened and when
Commerce
Payment semantics via HTTP 402 and pricing headers
Reference implementation and tools
Reference implementation, SDKs, and developer tools
Interoperability
PEAC is designed to interoperate with adjacent standards rather than replace them
HTTP 402 and x402
Commerce and signed records for machine-payable APIs
Agentic Commerce Protocol
Agentic commerce and transaction verification
AIPREF
AI preference standard for policy discovery and consent
Model Context Protocol
MCP tool verification and signed records for agent coordination
A2A Protocol
Agent-to-agent transactions with verifiable interaction records
All integrations
Explore all supported standards and protocols
Governance and contributing
PEAC is developed in public under the Apache-2.0 license. Originary (Poem, Inc.) is the primary maintainer today. Contributions are welcome. Supply chain hardening includes automated audit gates, lockfile drift detection, and a published security policy.
PEAC Protocol FAQ
Common questions about the open standard
PEAC is an open standard for publishing interaction terms and producing verifiable interaction records for automated requests.
Yes. The goal is independent implementations and consistent verification behavior across vendors.
PEAC is designed to interoperate. It focuses on the record and verification layer, while other standards cover payments, agent frameworks, or preference signaling.
Conformance defines deterministic rules and test vectors so multiple implementations produce verifiable, compatible results.
Start with the spec, conformance tests, and reference implementation. Contributions that improve interoperability and determinism are highest value.