Payment rails prove value moved. Signed records prove what it was for.
AI agents call paid APIs, buy data, trigger usage charges, settle invoices, and delegate work. A payment confirmation shows value moved. It rarely shows what the agent was allowed to do, which policy applied, or what result came back. Originary turns those events into signed records another party can verify without your logs.
- Issuer
- https://api.vendor.example
- Event
- authorized
- Action
- POST /v1/market-data/search
- Signature
- Ed25519 30cf81d6...
The rail proves the payment. The record proves the context.
A charge was authorized, captured, or settled between two parties.
The action, the policy or mandate, the result, the issuer, and the time, bound into one verifiable artifact.
When an agent pays, "did money move?" is the easy part.
- What was requested, and which policy or mandate applied?
- Who or what authorized the action?
- What result did the vendor return?
- Was the action allowed, denied, captured, refunded, or disputed?
- Can a customer, auditor, or partner verify the record later, without your systems?
A research agent calls a paid market-data API.
The payment rail shows a charge was authorized. The signed record shows the endpoint, the terms that applied, the payment reference, the result digest, the issuer, the time, and the signature a counterparty can check.
The record preserves the payment artifact as evidence: a signed settlement receipt travels in the record's proofs, and settlement metadata is carried as a digest by default so raw payment headers never enter the signed payload.
x402 owns the payment flow and its payment-native signed artifacts. Originary preserves those artifacts inside portable records and evidence bundles that verify offline.
npx -y @peac/cli verify ./payment-event.jws --public-key ./jwks.json
- Issuer
- https://api.vendor.example
- Event
- authorized
- Action
- POST /v1/market-data/search
- Agent
- research-agent-v3
- Policy
- terms:v3 sha256:81af2c...
- Ref
- rail reference - x402-style
- Result
- 200 sha256:9a3c1d...
- Time
- 2026-06-12T14:08:12Z
- Signature
- Ed25519 30cf81d6...
Records can sit around commerce workflows you already run.
Examples are interoperability surfaces, not partnership claims. Originary composes with payment rails, identity systems, and agent protocols.
What Originary does not do.
- It does not custody funds.
- It does not process payments.
- It does not replace your ledger or accounting system.
- It does not decide tax treatment.
- It does not require a chain, or another company to use Originary.
It issues, inspects, and verifies signed records from commerce workflows you already run.
Broader evidence coverage, same wire format.
Portable evidence beyond single signed records: the wire format stays stable while evidence coverage broadens.
Broader evidence coverage, not a new payment rail, gateway, or policy engine.
Start with one paid workflow where another party asks what happened.
A paid API call, an MCP tool that triggers a charge, a gateway decision, a payment authorization, or a dispute review.