VERIFIABLE RECORDS FOR AGENTS, APIS, AND GATEWAYS
Agent actions, on the record.
Originary creates portable signed records for agent actions, API calls, MCP tool runs, gateway decisions, payments, approvals and provisioning. Your team, customers, partners and auditors can verify those records without access to the source system's private logs.
- Payments
- Approvals
- Access decisions
- API calls
- Tool runs
- Changes
- Deletions
- Handoffs
- 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
- Developer verifiesdebugging, incident review
- Counterparty verifiesdispute, delivery, trust
- Auditor reviewscompliance, assurance
- Bundle exportsportable evidence pack
Logs stay local. Signed records travel.
Works across the agent and API stack
Interoperates across commerce, identity, and evidence
Ed25519 · JCS · Compact JWS · HTTP Message Signatures · Offline verification
Each side has logs. Neither side has evidence the other can independently verify.
A customer disputes a paid tool call. The provider has a gateway log. The customer has a charge reference. The tool server has a result. Those records live in different systems, under different operators, and may not establish the same facts.
The problem is not the absence of data. It is the absence of a bounded, transferable evidence set.
One evidence case, with its gaps stated.
Verification separates what the supplied records establish from what is missing, conflicting, or not evaluated. A complete happy path would misrepresent what real evidence looks like.
3 of 6 elements verified under the supplied key. One is linked, one is bounded, one was never supplied.
- Authorization referenceclient
- present
- Gateway decisiongateway
- signature verified
- MCP/API invocationtool server
- signature verified
- Payment-provider artifactpayment provider
- linked
- Delivery observationnot supplied
- missing
- Verification reportverifier
- complete with limitations
One evidence case, assembled from the systems that already observed the action.
Originary connects selected signed records and native artifacts, verifies them under an explicit key policy, and hands the bounded result to another party.
Start with one consequential workflow.
Paid MCP tools and APIs
Usage, result and provider-side service records for paid tool calls, with the provider artifact bound to the record.
See the paid-service workflowMCPmetered APIspayment artifactsGateway decisions
Record an allow, deny, or review decision with the policy or check that was applied, then verify it later outside the originating system.
See gateway evidencegateway policyroutingredactionAgent commerce
Authorization, mandate, payment and settlement-linked records connected into one reviewable commerce case.
See a paid-service disputemandatesauthorizationsettlementAudit and incident handoff
Move from internal logs to a portable evidence case for incident review, audits, counterparties and disputes.
See the handoff workflowtelemetryprovenanceincident exportProvisioning changes
Record account, resource, credential, subscription, and deployment events so they survive the system that made the change.
See provisioning recordscredentialsdeploymentssubscriptionsThe same record path supports customer reviews, incidents, audits and disputes. Agent actions, payment events, and provisioning use the same record format. More workflows.
See what each issuing system actually reported.
Every record is a bounded signed statement from one issuer. Each record family links to a worked example. Shipped PEAC samples can be generated and verified offline.
Shows the terminal allow, deny, or review the gateway observed, and the policy applied.
View worked exampleBinds the endpoint, the terms in force, and the result digest for a metered request.
View worked exampleRecords which tool ran, the argument digest, and what the server reported back.
View worked exampleTies an approval to exactly one proposal digest, so a changed action fails closed.
View worked examplePreserves which resource, credential, or subscription changed, and who issued it.
View worked exampleCarries the payment reference and mandate the service action was bound to.
View worked exampleA valid record can still be insufficient evidence.
- the supplied key validates the signature;
- the protected record bytes were not changed;
- disclosed content matches the digests bound by the record;
- the record contains the issuer-reported claims shown.
- that every relevant event was recorded;
- that the issuer's observation was complete or truthful;
- that the supplied key was authorized by the claimed issuer;
- that delivery occurred;
- that a legal or regulatory requirement was satisfied.
Built on an open record format, not a proprietary evidence database.
PEAC Protocol is an Apache-2.0 open protocol for portable signed interaction records. Teams can issue, verify, implement, and self-host PEAC independently of Originary.
- Portable signed records
- Offline verification
- Self-managed keys
- Independent implementations
- Conformance vectors
- No Originary callback required
- v0.16.3 current release
- 12,729 tests
- 290 conformance checks
- 36 packages on npm
- Apache-2.0 licensed
Start with one action another party needs to verify.
Bring one paid tool call, API request, gateway decision, or incident workflow. We’ll determine what can be recorded, which claims are supportable, and what evidence a separate recipient would actually need.
- Paid tool call
- API request
- Gateway decision
- Incident workflow