PEAC Protocol: the open standard for policy, payments, and receipts
Apache-2.0 licensed. Works anywhere. Adopt just the parts you need.
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
SDKs & Tools
Production-ready libraries and command-line tools
Governance & Contributing
Open Development
PEAC is maintained by Originary with community contributions welcome. Development happens in the open 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 LicenseDeploy PEAC yourself, or use Originary Cloud
Self-host with the open source stack, or add managed services like Trace, Gateway, Studio, and Verify API.