VERIFIABLE RECORDS FOR AGENTS, APIS, AND GATEWAYS
Agent actions, on the record.
Give important agent, API and tool actions a signed record you can verify later. Investigate incidents, answer customers and auditors, and share the record without exposing private logs.
- API calls
- MCP tools
- Agent actions
- Gateway decisions
- Payments
- Approvals
- Provisioning
- Built on PEAC Protocol
- Open source
- Offline verification
- Self-hostable
Originary records selected facts from a local system action, signs the record, and lets anyone verify it outside the system that created it. Verification supports audit, compliance review, dispute evidence, and partner handoff.
- API call
- MCP tool run
- Agent action
- Gateway decision
- Payment event
- Provisioning event
- Your team verifiesdebugging · incident review
- Customer or partner verifiesshared records · disputes
- Security or audit reviewsaudit · compliance review
Logs stay local. Signed records travel.
Composes with
Interoperates across commerce, identity, and evidence
Ed25519 · JCS · Compact JWS · HTTP Message Signatures · Offline verification
The record is there when you need it.
An incident happens.
See what the system recorded without reconstructing the whole story from separate logs.
A customer asks what changed.
Send them a record they can inspect instead of screenshots from your dashboard.
An auditor asks for evidence.
Share the relevant records without opening production systems.
Two systems disagree.
Compare what each one recorded instead of relying on either side's private log.
Record the action. Verify it anywhere.
Record
Your agent, API, tool server or gateway signs selected facts about the action.
Verify
Check the record later with the public key you expect.
Share
Send it to another team, customer or reviewer without sharing private logs.
- Action
- Refund approved
- System
- support-agent
- Time
- 2026-04-17 08:01:31 UTC
- Result
- refunded
- Issuer
- support-agent.example
- Demo signature
- II1J0aGhPVY8SaJ4SE9AJ_BC…
Share the record, not your logs.
Logs are for running your system. PEAC records are built to travel. Send one to a customer, partner, auditor or another service and let them verify it separately.
No Originary account is required to verify a PEAC record.
A record for every important action.
PEAC uses the same core record model across agents, APIs, tools, gateways, payments and provisioning.
What tool ran, and what result did it report?
View exampleWhat did the API report receiving and returning?
View exampleWhat action did the agent report taking?
View exampleWas the request allowed, blocked, redacted or reviewed?
View exampleWhat did the payment system report?
View exampleWhat account, credential or resource changed?
View exampleReviewing a whole incident or transaction? See how related records can be brought together →
Know exactly what was verified.
Verification tells you
- the supplied key validates the signature;
- the protected record has not changed;
- evaluated content matches what the record binds.
It doesn't automatically tell you
- that every relevant event was recorded;
- that the issuer or every statement should be trusted;
- that an external event or legal requirement was satisfied.
Clear verification, without claiming more than the record establishes.
Open protocol. No Originary required.
PEAC is the Apache-2.0 protocol behind the records. Issue and verify records yourself, keep your own keys, and run verification locally.
Open source
Inspect and implement it yourself.
Self-hostable
Keep issuance and keys under your control.
Local verification
Verify without uploading the record to Originary.
Conformance-tested
Use public requirements and fixtures across implementations.
Start here
Choose what you want to do.
Verify a record
Check a signed record locally.
Open verifierAdd records to MCP
Create signed records for important tool calls.
MCP quickstartAdd records to an API
Issue records alongside API interactions.
API quickstartRecord gateway decisions
Record allow, deny, redaction and review decisions.
Gateway guide
Put your first action on the record.
Tell us what the system does and who needs to review it. We'll help you map the smallest useful PEAC integration.