PEAC
v0.12.3stableReleases

Start Here

PEAC is most useful where logs are not enough: payments, cross-boundary verification, audit, dispute review, and multi-agent workflows.

I run an API or HTTP service

Issue signed receipts proving what terms applied and what happened.

  1. 1
    Installpnpm add @peac/middleware-express @peac/crypto @peac/protocol
  2. 2
  3. 3
@peac/middleware-express@peac/protocol@peac/crypto

I want to verify a receipt

Verify a receipt offline with just a public key.

  1. 1
    Installpnpm add @peac/protocol @peac/crypto
  2. 2
  3. 3
@peac/protocol@peac/crypto

I run an MCP server

Add receipt operations to your MCP server, or attach receipts to tool responses.

  1. 1
    Try it nownpx -y @peac/mcp-server --help
  2. 2
  3. 3
@peac/mcp-server@peac/mappings-mcp

I build A2A agents

Carry receipts across Agent-to-Agent Protocol flows.

  1. 1
    Installpnpm add @peac/mappings-a2a @peac/protocol @peac/crypto
  2. 2
  3. 3
@peac/mappings-a2a@peac/protocol

x402 and payment proofs

Verifiable payment and settlement evidence for machine-to-machine commerce.

Audit, dispute, and governance

Signed evidence for audit, dispute review, or governance workflows.

Core Concepts

Receipt
A signed JWS (interaction-record+jwt) proving what terms applied and what happened
Kind
evidence (records what happened) or challenge (requests proof from a peer)
Type
Reverse-DNS identifier for what the receipt represents (e.g., org.peacprotocol/payment)
Extensions
Typed data groups (12 groups: commerce, access, identity, etc.) carrying domain-specific evidence
Offline verification
Receipts verify with just the public key; no network calls required
Looking for the full code walkthrough? Reference Quickstart has issue, verify, and middleware examples.