Records

Signed records for the actions your software takes.

APIs, MCP tools, agents, gateways, payments and provisioning use one record format, so a single verifier checks all six.

Payment event signed

event
authorized
mandate
sha256:77ab90…
time
14:08:12Z
signature
Ed25519

Gateway decision signed

request
export_billing
result
denied
time
14:10:40Z
signature
Ed25519

MCP tool run signed

tool
search_docs
result
ok
time
14:08:11Z
signature
Ed25519
MCP tool run

When an MCP tool runs, what evidence leaves the server?

Answers which tool was called, under what policy, and what result digest came back. Full MCP page.

Verify it
npx -y @peac/cli@0.16.4 verify ./mcp-tool-run.jws --public-key ./jwks.json
Tamper case

Change the tool name, the result digest, or one character of the signature and verification fails with E_INVALID_SIGNATURE.

MCP tool runverified offline
Issuer
https://mcp.vendor.example
Tool
tools.call search_docs
Policy
tool-policy:v2 sha256:4e21b8...
Result
ok sha256:9a3c1d...
Time
2026-06-12T14:08:11Z
Signature
Ed25519 7d40e2c9...
carried in MCP response metadata - verifiable without the server
API call

Show what your API reported, without opening your logs.

Answers which endpoint was called, which terms applied, and what result the API returned.

Verify it
npx -y @peac/cli@0.16.4 verify ./api-call.jws --public-key ./jwks.json
Expected
Signature valid (offline).
Flip one byte and verification fails. A failed check is also evidence.
API callverified offline
Issuer
https://api.vendor.example
Action
POST /v1/market-data/search
Policy
terms:v3 sha256:81af2c...
Result
200 sha256:9a3c1d...
Time
2026-06-12T14:08:11Z
Signature
Ed25519 b2c1a4e8...
sample record - demo signature
Decoded payload
{
  "iss": "https://api.vendor.example",
  "action": "POST /v1/market-data/search",
  "policy": { "ref": "terms:v3", "digest": "sha256:81af2c..." },
  "result": { "status": 200, "digest": "sha256:9a3c1d..." },
  "occurred_at": "2026-06-12T14:08:11Z"
}
Gateway decision

A refused request can still be recorded.

Answers what the gateway decided before a request was routed, throttled or refused. A denied call still gets a signed record, so reviewers can see what was refused without reading your gateway logs.

Verify it
npx -y @peac/cli@0.16.4 verify ./gateway-deny.jws --public-key ./jwks.json
Expected
Signature valid (offline).
Gateway decisiondecision: denied
Issuer
https://gateway.vendor.example
Request
tools.call export_billing
Policy
tool-policy:v2 sha256:4e21b8...
Result
denied - policy_violation
Time
2026-06-12T14:10:40Z
Signature
Ed25519 e02d7f15... valid
signed refusal - verifiable like any other record
Agent action

What did the agent do, and what was it bound to?

Answers which agent acted, which input digests, and which mandate or policy version the action was bound to.

Verify it
npx -y @peac/cli@0.16.4 verify ./agent-action.jws --public-key ./jwks.json
Tamper case

Swap the mandate digest for a newer version after the fact and the record still shows the digest that was actually bound at signing time.

Agent actionverified offline
Issuer
https://runtime.vendor.example
Agent
research-agent-v3
Action
summarize_filing
Input
sha256:c41b09...
Policy
mandate:v2 sha256:5fe013...
Time
2026-06-12T14:09:02Z
Signature
Ed25519 91bc44a0...
sample record - demo signature
Payment event

Tie a payment to the action and mandate it paid for.

Answers what a payment was tied to. The payment provider reports value movement; the record binds the action, the mandate, and the observed payment state to one signed artifact. Paid APIs and agent commerce page.

Verify it
npx -y @peac/cli@0.16.4 verify ./payment-event.jws --public-key ./jwks.json
Tamper case

Point the record at a different payment reference after settlement and the original reference stays bound under the signature.

Payment eventverified offline
Issuer
https://api.vendor.example
Event
authorized
Action
POST /v1/market-data/search
Ref
rail reference - x402-style
Mandate
sha256:77ab90...
Time
2026-06-12T14:08:12Z
Signature
Ed25519 30cf81d6...
observation record - not a payment instruction - no funds custody
Provisioning event

Who changed what, and which system says so.

Answers which account, resource, credential, or subscription event occurred, and who issued it. Useful long after dashboards and sessions are gone. Full provisioning page.

Verify it
npx -y @peac/cli@0.16.4 verify ./provisioning-event.jws --public-key ./jwks.json
Tamper case

Changing a later export does not alter the issuance time and event details bound by the signature.

Provisioning eventverified offline
Issuer
https://ci.vendor.example
Event
credential.rotated
Resource
deploy-key-7
Actor
release-pipeline
Time
2026-06-12T03:00:00Z
Signature
Ed25519 4ab2c7e1...
sample record - demo signature

What verification means

A valid signature establishes three things and leaves the rest to you.

It tells you the record is intact and was signed by the key you supplied. Whether the record is complete, and whether to trust the issuer, are still your questions.

ResultSignature valid

  • CheckedThe supplied key validates the signature.
  • CheckedThe protected record has not changed since it was signed.
  • CheckedEvaluated content matches what the record binds.
  • Not checkedWhether every relevant event was recorded.
  • Not checkedWhether the issuer, or each statement, should be trusted.
  • Not checkedWhether an external event or legal requirement was satisfied.

Verify any of these yourself.