Skip to main content
Open Source • Apache-2.0

PEAC Protocol: an open protocol for policy, payments, and receipts

Apache-2.0 licensed. Works anywhere. Adopt just the parts you need.

Path to Standard Adoption

We are working toward multiple independent implementations before 1.0

Pre-1.0

Originary reference implementation

Multiple implementations

Independent conformant implementations

Post-1.0

Broad adoption and ecosystem

No single implementation has privileged status. Originary is one implementation; we welcome others.

PEAC is designed for adapter-based interoperability. Multiple implementations ensure the protocol remains neutral, open, and resilient.

Why PEAC

Seven pillars of infrastructure for the agentic web

Access

Declare who can use your resources and under what conditions

Attribution

Every request carries verifiable identity and intent

Consent

Explicit, machine-readable consent before access

Commerce

Native payment semantics via HTTP 402 and pricing headers

Compliance

Audit trails and receipts for regulatory requirements

Privacy

Minimal disclosure and selective transparency

Provenance

Cryptographic proof of what happened and when

Governance & Contributing

Open Development

Developed in public with community contributions. Originary (Poem, Inc.) is the primary maintainer today. Development happens on GitHub with semantic versioning and public roadmaps.

License & Use

Apache-2.0. No CLA required for small fixes; DCO accepted. PEAC is neutral and adapter-friendly, Originary is one implementation.

View License

Deploy PEAC yourself, or use Originary Cloud

Self-host with the open source stack, or add managed services like Trace, Gateway, Studio, and Verify API.