Originary™ for AI
Publish peac.txt, settle via x402 (or Stripe/credits/fiat/stablecoin/on-chain), and present a Receipt on every request - proof of access, consent, attribution, privacy, and payment.
Use Originary to instrument agentic commerce, AI consent tracking, and AI provenance tracking for every agent-to-agent transaction. Whether you’re enabling agentic transactions or building for the automated economy, PEAC-Receipts provide verifiable proof of every interaction.
Why Originary vs generic agent frameworks
Not another framework.
Keep your MCP/A2A tools and orchestrators - Originary adds verifiable Receipts so every access has proof of terms, consent, attribution, privacy, and payment.
Rail-neutral payments (x402 first).
Settle via x402 by default, or Stripe/credits/fiat/stablecoin/on-chain via adapters - no lock-in, same receipt format.
Compliance by construction.
Receipts encode purposes, retention windows, attribution & consent flags - turn audits into evidence, not meetings.
Drop-in at the edge.
Enforce at Cloudflare/Vercel/AWS edge with minimal overhead; no app rewrite required.
Interoperable with MCP/A2A.
Pass a PEAC-Receipt alongside existing tool/resolver calls; verify before data leaves your origin.
Simple, web-native.
A tiny /.well-known/peac.txt declares your terms; everything else is adapters and a signed receipt.
MCP/A2A Integration
Add Receipts beside your tools/resolvers, not instead of them - send a PEAC-Receipt with requests; verify at the edge.
Works with
Frequently Asked Questions
What are PEAC-Receipts?
PEAC-Receipts are cryptographically signed, verifiable proofs of API access, payment, consent, and attribution. Each receipt contains evidence of the transaction terms, payment confirmation, usage scope, and compliance metadata - all in a machine-readable format that AI agents and auditors can verify. They work across HTTP 402, x402, MCP, and A2A protocols.
How does Originary help with AI compliance and provenance?
Originary provides AI provenance tracking and AI compliance infrastructure through PEAC-Receipts. Every access generates a signed receipt containing consent flags, attribution data, retention windows, and payment proof. This creates an audit trail for regulatory compliance, proving what data was accessed, by whom, for what purpose, and under what terms - critical for AI governance and agentic commerce transactions.
No affiliation with other businesses using similar names.