Prove what
agents did
Originary verifies requests, applies policy, and returns signed records you can prove later, across teams, vendors, and audits.
Sample record. Verified with issuer public key only.
Who called. What happened. Where's the proof?
An agent running on Company A's infrastructure calls Company B's inventory API. Company B's gateway returns a signed record proving the request was authorized under the published terms. Three weeks later, when a billing dispute arises, Company B exports that record. Company A's auditor verifies it offline using the issuer's public key. No dashboard access needed. No phone call. No screenshot.
Logs explain behavior. Records prove decisions.
Logs are useful for debugging inside your systems. They are weak evidence outside them. Originary returns signed records another party can inspect and verify independently.
| Need | Logs / traces | Originary |
|---|---|---|
| Debug system behavior | Yes | Partial |
| Make access decisions | Limited | Yes |
| Keep an exportable record | No | Yes |
| Support cross-team review | Weak | Yes |
| Open standard underneath | No | Yes |
Debug system behavior
Make access decisions
Keep an exportable record
Support cross-team review
Open standard underneath
Originary adds:
Built for the systems agents touch
Originary is for teams operating APIs, tools, gateways, MCP servers, and review workflows. If your systems receive automated requests, you need evidence that survives beyond your own dashboards.
An agent books a resource through your API
You need to know who authorized it, under what policy, and prove the decision later when the charge is disputed.
An MCP tool call modifies production data
The tool host needs a signed record of what was requested, what was allowed, and what the agent actually did.
A partner asks for proof of an agent interaction
You export a portable record they can verify independently, offline, without calling your systems.
An auditor reviews agent-driven transactions
Compliance needs exportable evidence tied to the policy that applied at decision time, not just logs.
Works with your existing gateway, auth, payments, and observability stack.
Built to be verified without us
Every record should survive vendor boundaries. Originary can issue and manage records in production, but verification should remain local, portable, and independent.
Self-hostable
Run on your own infrastructure. No external dependency.
Offline verification
Verify with the public key alone. No network required.
Exportable records
Inspect, share, archive, and use in disputes.
Open standard
PEAC Protocol, Apache-2.0. Portable across vendors.
Ed25519 signatures
Every record is signed with Ed25519 and independently verifiable.
Audit and dispute ready
Timestamped evidence for compliance and procurement.
Recognized in x402 ecosystem
PEAC receipt verification contributed to technical discussions with the Coinbase x402 protocol team.
Evidence is not keeping up with automation
Agents are crossing boundaries
APIs, tools, and MCP servers handle agent traffic from organizations they do not control. Standard proof is missing.
Compliance is catching up
Compliance and review expectations for automated decisions are rising. Auditable records will be expected.
Disputes need portable artifacts
When an incident involves multiple teams, partners, or vendors, the party with exportable evidence resolves faster than the party with screenshots.
Deploy Originary. Keep your records portable.
Originary is the product you deploy. PEAC is the open standard that keeps your records portable across systems and vendors. No lock-in.
Ed25519 signatures, verified offline with a public key
29 packages on npm, 6,664 tests
Offline-verifiable with public key alone
Apache-2.0, self-hostable, vendor-neutral