Prove what
agents did
Originary helps teams return signed records for AI agents, APIs, MCP, and automated workflows, so another party can verify what happened without trusting a dashboard.
Originary Verify is the fastest way to operationalize PEAC in production.
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, priced APIs, and review workflows. If your systems receive automated requests, you need proof 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 signed record they can verify independently, offline, without calling your systems.
An auditor reviews agent-driven transactions
Compliance needs an exportable record 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, offline, and independent.
Self-hostable
Run on your own infrastructure. No external dependency required.
Offline verification
Verify with the public key alone. No network call required.
Exportable records
Inspect, share, archive, and use in disputes, reviews, and audits.
Open standard
PEAC Protocol under Apache-2.0. Portable across vendors and implementations.
Ed25519 signatures
Every record is signed with Ed25519 and independently verifiable.
Audit and dispute ready
Timestamped records for compliance, procurement, and incident review.
Built for real workflows
Designed for AI agents, APIs, MCP, priced API access, and cross-boundary automated systems.
Records are not keeping up with automation
Cross-boundary agent activity
Agents now act across APIs, tools, and runtimes owned by different teams and vendors. Signed records travel with the action so another party can verify what happened independently.
Growing audit and review expectations
Teams are increasingly expected to prove what automated systems did. Logs describe behavior. Signed records prove decisions.
Faster dispute resolution
When records are exportable and offline-verifiable, disputes resolve faster than when everyone depends on the dashboard owner to confirm what happened.
Deploy Originary. Keep your records portable.
Originary is the production product surface. PEAC is the open standard underneath. You can self-host, verify offline, and keep your records portable across teams and vendors.
Offline-verifiable with a public key alone
Apache-2.0 and self-hostable
Built for APIs, MCP, and automated workflows
Frequently asked questions
Deploy Originary. Keep your records portable.
Originary is the production product surface. PEAC is the open standard underneath. You can self-host, verify offline, and keep your records portable across teams and vendors.