What is Originary?
Originary builds PEAC: an open standard for publishing terms and issuing verifiable records for agent interactions.
No gatekeepers. No lock-in. No centralized control.
Open standard. Apache-2.0. Self-hostable. Designed for independent implementations.
The problem
Agents need accountability: clear terms, enforceable decisions, and durable evidence of what happened. As of v0.10.0 (January 2026), PEAC provides this through signed receipts and verifiable policy snapshots.
Without portable records, compliance is screenshots and disputes are opinions. (Common mistake: treating server logs as proof - they're unilateral and easily altered.)
PEAC makes interactions inspectable, auditable, and interoperable.
What Originary does
Originary maintains the reference standard and production tooling for turning decisions into verifiable records. Publish terms, enforce them, verify independently.
Publish terms
With a machine-readable policy surface (recommended: /.well-known/peac.txt)
Enforce decisions
Using standard HTTP semantics (allow/deny/conditional requirements, including optional 402 flows)
Return a record
As a signed receipt (PEAC-Receipt) that can be verified offline and stored as evidence
How PEAC makes records portable
PEAC is designed so any implementation can produce the same verifiable outcome: a policy snapshot plus a signed receipt. The receipt is the portable artifact; verification does not require Originary to be online.
Adapters keep the core standard neutral across protocols and payment rails.
Policy surface (peac.txt)
Publish terms in one place so agents and services can discover requirements before access.
Receipt format (PEAC-Receipt)
Return a signed record with stable claims for what occurred, under which terms, and with what authorization evidence.
Verification & conformance
Verify receipts offline or via a verification endpoint, and validate policy conformance to reduce ambiguity in audits and disputes.
Who this is for
PEAC and Originary are built for teams that need interaction evidence to be durable and verifiable across environments.
APIs and SaaS platforms
Prove access decisions and delivery outcomes
Publishers and data providers
Publish clear terms and require verifiable compliance
Agent developers
Rely on a portable receipt that works across rails and environments
Security, compliance, and policy teams
Get evidence trails that stand up in reviews
Originary and PEAC Protocol
PEAC Protocol is open source and designed for independent implementations.
Originary is a steward and a production-grade implementer of the standard, not the standard itself. The goal is a credible, interoperable ecosystem where verification works the same way everywhere.
Name and affiliation
Originary is a brand of Poem, Inc. In the U.S., Poem, Inc. is not affiliated with other organizations using similar names.
Imprint / LegalLimitations
- PEAC does not enforce compliance. It provides evidence of what the issuer claims occurred.
- Receipt contents are issuer-controlled. Verifiers trust the issuer's representation, not an oracle.
- Version 0.10.0 wire format may change before 1.0. Cross-version compatibility is not guaranteed.
- Key compromise invalidates all receipts signed with that key (standard PKI limitation).
- PEAC provides evidence for disputes, not adjudication. Resolution is out of scope.
FAQ
Do receipts replace payment rails?
No. Rails settle value; receipts are portable records that prove what was authorized and what occurred.
Is PEAC-Receipt the canonical HTTP header name?
Yes. PEAC-Receipt is the canonical receipt header for PEAC.
Does verification require Originary?
No. Receipts are designed for offline verification using public keys and published policy.
Is PEAC stable?
PEAC is at version 0.10.0; the goal is to earn 1.0 through multi-implementation, conformance, and standards work.
Start building
Explore the standard, try the demo, or deploy the reference stack. If you're integrating at scale, contact us for implementation support and hosted options.