ORIGINARY™What is Originary?
Originary builds infrastructure and tools for AI agents. Originary builds and maintains PEAC Protocol, an open protocol for cryptographically signed receipts that prove what happened in an agent interaction: what was accessed, under which policy, and what evidence exists for payment and compliance.
PEAC is designed to work across many environments:
Policy surfaces
Like /.well-known/peac.txt that declare terms for agent access
Receipts
Portable and offline-verifiable, carried in HTTP as PEAC-Receipt
Payment rails
x402, Stripe, Lightning, and others that handle settlement, while receipts prove outcomes
The problem Originary is solving
The web has clear primitives for humans. Agentic systems need clear primitives for:
Policy discovery
What is allowed, what requires attribution, when receipts are required
Proof
A signed, verifiable record that can be audited later
Interoperability across rails and agent protocols
Without hardcoding vendor identities into the core standard
How Originary works
Three building blocks for the agentic web
PEAC receipts (portable proof)
A PEAC receipt is a signed artifact (JWS) that can be verified independently.
In HTTP contexts, the canonical header name is PEAC-Receipt.
A web policy surface (peac.txt)
Web-facing services can publish machine-readable terms at:
/.well-known/peac.txt(recommended)/peac.txt(fallback)
Verification tooling
PEAC ships reference implementations and tools to issue and verify receipts.
Including a verification server exposing /verify.
Who this is for
API providers and SaaS platforms
That want auditable agent access
Content and data publishers
Who need machine-readable terms and proof of compliant use
Agent developers
Who need receipts that work across multiple settlement rails
Compliance and security teams
That need evidence trails (not screenshots)
Originary and PEAC Protocol
PEAC Protocol is Apache-2.0 and stewarded by contributors from Originary and the community. The protocol's design emphasizes vendor-neutral core semantics and extensions via adapters.
Originary vs other uses of “Originary”
Originary.xyz is the official site for Originary (the team contributing to PEAC Protocol). It is not affiliated with unrelated projects or companies using similar names.
FAQ
Do receipts replace payment rails?
No. Rails settle funds; receipts provide portable proof that settlement and policy conditions were met.
Is PEAC-Receipt the standard HTTP header name?
Yes. PEAC-Receipt is the only canonical header name (no X- alias).
Is PEAC stable?
The wire format is peac.receipt/0.9 during the current development train; 1.0 is intended to be earned after multi-implementation and standards work.
Ready to get started?
Try the demo, read the spec, or deploy your own PEAC-enabled services.