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.
For API providers, agent platforms, and security/compliance teams operating across org boundaries.
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 recordVerify the system
Designed for disputes and audits
Originary doesn't replace your agent framework or payment rail. It makes interactions provable and portable.
Ready to build?
Install the packages, add middleware or MCP tools, and start issuing verifiable records. Open source, self-hostable, Apache-2.0.
Frequently asked questions
Frequently asked questions about Originary, PEAC Protocol, and infrastructure for the AI and agentic web.
What is Originary?
Originary builds infrastructure and tools for the AI and agentic web.
What does Originary do?
Originary helps teams build trustworthy automated systems with open standards, developer tooling, and verifiable interaction infrastructure.
What is PEAC Protocol?
PEAC is the open standard Originary stewards for verifiable interaction records across agents, APIs, and services.
Who is Originary for?
Originary is for developers, platforms, and companies building AI products, agents, APIs, and agentic workflows.
Why does the agentic web need new infrastructure?
As AI agents interact across tools, services, and organizations, teams need better infrastructure for trust, verification, policy, and portable records.