Verifiable recordsfor automated
interactions.
Agents cross org boundaries. Logs don't.
Originary turns API calls, tool runs, and agent handoffs into portable signed records you can verify independently, even offline. Publish terms at /.well-known/peac.txt.
OSS packages. Self-hostable. Verification does not require Originary to be online.
- 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
Three steps to verifiable interactions
Publish terms, check requests, return a signed record
Publish terms
Machine-readable policy
Add a peac.txt file to your domain. It declares access rules, pricing, and consent terms that agents and MCP clients discover automatically.
See templateCheck requests
Middleware or MCP tools
Evaluate each request against your policy. Allow, deny, or return HTTP 402 to request payment. Works at the edge, origin, or inside an MCP tool call.
Add middlewareReturn a signed record
Portable proof
Every interaction produces a signed record that verifies offline with your public key. Bundle records into evidence archives for audit or handoff.
Verify a recordShip today, verify anywhere
Open-source packages for issuing, capturing, and verifying signed interaction records.
MCP Server
AvailableAI agent verification tools
Five tools for Claude, Cursor, and any MCP client. Verify, inspect, and decode records. Issue and bundle with capability-based access control.
Gateway
AvailableEdge gateway for AI agents
Enable HTTP 402 payment-required flows and issue signed records at the edge or origin.
Verify
AvailableCryptographic verification
Offline and hosted record verification with JWKS support and policy validation.
Capture
AvailableDurable interaction evidence
File-backed spool and deduplication stores for Node.js. Capture interaction evidence with durable, crash-safe storage.
Trace
PreviewAudit trails and provenance
Audit exports and evidence views derived from signed interaction records.
Studio
PreviewPolicy dashboard
Policy management, interaction analytics, and governance views for deployments.
Verify the system
Designed for disputes and audits
Originary doesn't replace your agent framework or payment rail. It makes interactions provable and portable.
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?
Install the packages, add middleware or MCP tools, and start issuing verifiable records. Open source, self-hostable, Apache-2.0.