What Did My Agent Do?

An agent triggered a payment. Can you prove what happened?

Payment logs help you debug. A signed record helps another party verify what was authorized vs what was charged.

Separate what was authorized from what was captured.
See which evidence is missing for a dispute.
Understand how signed records travel across organizational boundaries.

Example input

An agent triggered a payment authorization of $247.00 via a third-party payment API.

What the checker shows

Missing: authorization-vs-capture boundary, finality/settlement proof, authorization policy at decision time, payer/agent identity boundary, signature.

What is missing for cross-party proof

Evidence	Status
What was authorized	often missing as signed evidence
What was actually captured	missing
Finality / settlement proof	missing
Authorization policy at decision time	missing

Close the gap

import { issue } from '@peac/protocol';
// after handling the request, sign a record of what happened:
const { jws } = await issue({
  iss: 'https://your-service.example.com',
  kind: 'evidence',
  type: 'org.peacprotocol/commerce-authorization-observed',
  privateKey, kid,
});
res.setHeader('PEAC-Receipt', jws);

Analyze a payment event →

Show your records are verifiable

Issuing signed records already? Add a badge to your README:

[![agent records: verifiable](https://whatdidmyagentdo.com/badge.svg)](https://whatdidmyagentdo.com)

PEAC observes payment-adjacent flows (such as x402 responses and AP2 mandate references) without executing settlement.

Open the verifier · Full checker · How it works · PEAC standard