How a signed record is made and checked
Your system signs selected facts about an action. The record is kept apart from the logs and the service that produced it, so anyone with the issuer's public key can check it offline.
- Your systemobserves the action
- Signed recordfacts, policy, result, time, issuer, signature
- Their machinechecks it offline
Signature valid, offline
- 01
Observe
The system that handles the action, such as an API, MCP server, gateway or payment processor, observes what was requested, which policy applied and what came back.
the issuer is the system that observed the action - 02
Issue
At the moment the system acts, it signs a record that binds selected facts, such as the request and response digests, the policy in force, the issuer, and the time, to a key it controls. Private logs stay private.
sign() -> interaction-record+jwt - 03
Verify
Any party checks the signature and the bound digests offline, outside the system that produced them, with no access to your logs or dashboard, under a supplied key or an explicit expected-issuer policy.
verify --public-key -> valid (offline) - 04
Hand off
Optionally, package the records, native artifacts, and verification results into one evidence case for a customer, auditor, or partner to inspect independently.
records + artifacts + report -> evidence case
The same four steps, wherever the action happens.
Pick a surface to see what the record binds, how it is carried and which questions it answers.
API call
The API response comes back with a signed record of the request, the response and the terms that applied.
PEAC-Receipt header. Nothing else about the request or response changes. The publisher's terms live at /.well-known/peac.txt, and the record binds a digest of the policy that was in force at the moment of the call.The record binds
- resource + method
- request digest
- response digest
- policy digest
- issuer + key id
- time + unique id
carrier: PEAC-Receipt header. discovery: /.well-known/peac.txt.
It said something different yesterday
A response edited after the fact fails the bound digest. The record freezes what was actually served.
Metering and usage disputes
Each call yields its own receipt, so usage claims can be checked against signed records instead of one side's counters.
Those were not the terms
The policy digest pins the exact published terms in force at call time.
Try it on the sample record.
Verify the sample, then change the result field and verify again. The check runs in your browser.
Decoded record
Refund approved
{ "action": "refund_approved", "iat": 1776412891, "iss": "https://support-agent.example", "result": "refunded", "sub": "crm.update" }
Signed token · compact JWS
eyJhbGciOiJFZERTQSIsImtpZCI6Imh0dHBzOi8vc3VwcG9ydC1hZ2VudC5leGFtcGxlLy53ZWxsLWtub3duL2p3a3MuanNvbiNkZW1vLTEiLCJ0eXAiOiJpbnRlcmFjdGlvbi1yZWNvcmQrand0In0.eyJhY3Rpb24iOiJyZWZ1bmRfYXBwcm92ZWQiLCJpYXQiOjE3NzY0MTI4OTEsImlzcyI6Imh0dHBzOi8vc3VwcG9ydC1hZ2VudC5leGFtcGxlIiwicmVzdWx0IjoicmVmdW5kZWQiLCJzdWIiOiJjcm0udXBkYXRlIn0.II1J0aGhPVY8SaJ4SE9AJ_BCWEDs9bg5goG5OYL2AagxTmXNPxNxu2NloFSFkZlh1oIF-ocuHuoAVmGXyEetDQ
Issuer's public key · Ed25519
AuFbhNMoYUl-48DqDWzihJVBED3M1lD8v3qARLZRD4s