Choose the surface that fits your evidence workflow
Most teams start with Agent Auditor or Gateway 402. Add MCP Server for AI clients, Trace for monitoring, or lower-level building blocks for custom flows.
Each product handles a different stage of the evidence lifecycle.
Agent Auditor
Open any signed interaction record and see who acted, what happened, and whether the proof is genuine. Browser or CLI.
- Visual record inspector
- Signature verification
- Browser and CLI
- Offline capable
Gateway 402
Enforce access and payment policy at the edge. Issue signed records on every response.
- Edge deployment
- HTTP 402 challenge flows
- Signed interaction records
- Rail-neutral design
MCP Server
Five verification tools for Claude, Cursor, and any MCP client. Verify, inspect, and decode records offline.
- 5 MCP tools
- Offline verification
- Capability-based ACL
- Claude Desktop and Cursor
Verify
Validate signatures offline using the issuer's public key. No API callback required.
- Ed25519 signature verification
- Offline verification
- JWKS support
- Policy binding validation
Trace
Monitor agent traffic accessing your APIs and content. Export signed evidence.
- AI agent identification
- Traffic observation
- Evidence export
- Audit log generation
Building blocks
Lower-level packages for custom integrations
Capture
File-backed spool and deduplication stores for Node.js. Durable, crash-safe storage and structured counters.
Declare
Generate peac.txt, AIPREF headers, and human-readable policy pages from a single YAML config.
Built on PEAC, an open standard
PEAC is the open standard for verifiable interaction records. Originary is one product built on top of it. Every product above uses the PEAC open standard (Apache-2.0). Self-host the entire stack, use Originary, or build your own conformant implementation. No lock-in.
Start with the OSS packages
Install from npm. Deploy to your infrastructure. Reach out when you need enterprise support.