Verify agent interactions.Instantly.
APIs and sites lack a portable, third-party verifiable way to show what an agent accessed and under which terms.
Originary issues signature-verified records you can verify offline and export for audits.
- No portable record of what an agent accessed
- Disputes rely on server logs alone
- Terms and consent are implicit, not verifiable
- Every interaction produces a signature-verified record
- Disputes use portable, third-party verifiable evidence
- Terms, consent, and attribution are explicit and auditable
Start here
Three steps to verifiable interactions
Publish terms, enforce decisions, prove what happened
Publish policy
Machine-readable terms
Deploy a policy at /.well-known/peac.txt defining access terms and payment requirements. Agents discover it automatically.
Enforce at edge
Real-time decisions
Allow, deny, or request payment before serving responses. HTTP 402 status codes trigger programmatic settlement.
Return receipt
Verified record
Sign and return a PEAC-Receipt. Verifies offline with your public key. Portable across any system.
// Signature-verified record
PEAC-Receipt: eyJhbGciOiJFZDI1NTE5...
// Decoded payload
{
"v": "0.10.0",
"iss": "api.example.com",
"sub": "agent:example-client",
"iat": 1703894400,
"action": "api.query",
"status": "success"
}Built for the agentic economy
Production components for policy enforcement, optional settlement flows, and receipt verification.
Gateway
Edge enforcement for the agentic web
Enable HTTP 402 payment-required flows and issue PEAC receipts at the edge or origin.
Verify
Cryptographic proof validation
Offline and hosted receipt verification with JWKS support and policy validation.
Trace
Audit trails and provenance
Comprehensive audit exports and evidence views derived from PEAC receipts.
Studio
Builder dashboard
Operate receipts at scale with dashboards, exports, and policy tooling.
Verify the system
Designed for disputes and audits
Frequently Asked Questions
Originary builds tools and services for issuing and verifying PEAC interaction records. PEAC is the open standard; Originary is one production-grade implementation.
A PEAC receipt is a signed record of an automated request and the decision made under published terms. It is designed to be portable so third parties can verify it later.
No. Verification is designed to work offline using public keys and the published policy surface. Originary can optionally host verification infrastructure.
Automated requests usually leave logs that are not portable or independently verifiable. PEAC receipts make compliance, audits, and disputes evidence-based rather than screenshot-based.
Verify a sample receipt in the verifier, then follow the quickstart to issue receipts from a real endpoint.
Ready to build?
Deploy the reference stack or use hosted Originary for production SLAs. Open source and self-hostable.