Choose Your Path
PEAC Protocol serves different roles depending on what you're building. Each path below includes the packages you need, the guides to follow, and the concepts to understand.
If you're exploring PEAC for the first time, start with the API / Service (Issuer) path. It covers the core flow -- issuing and verifying receipts -- and everything else builds on top of it.
API or service (Issuer)
You want to issue receipts that prove what happened during interactions with your service.
Every API response gets a signed PEAC-Receipt header. Clients and agents can verify these receipts offline, without calling back to your service.
- Install
@peac/protocol-- the core issuance and verification API - Run the quickstart -- issue and verify your first receipt in 5 minutes
- Add Express middleware -- auto-issue receipts on every response
- Publish your policy -- make your terms discoverable at
/.well-known/peac.txt
Key packages: @peac/protocol, @peac/middleware-express, @peac/crypto
AI agent or client (Consumer)
You want to collect, verify, and audit receipts from services your agent interacts with.
Receipts let your agent prove what it did, what it paid, and what terms it operated under. Verification is deterministic and runs entirely offline.
- Understand receipts -- the signed JWS format and lifecycle stages
- Learn verification -- 12 checks, zero network calls to the issuer
- Export evidence bundles -- portable
.peac.tar.gzarchives for audits - Use the CLI -- verify and inspect receipts from the command line
Key packages: @peac/protocol, @peac/capture-core, @peac/cli
MCP integration
You want to verify or issue receipts in MCP-compatible AI environments.
The PEAC MCP server exposes five tools -- verify, inspect, decode, issue, and bundle -- so AI agents can work with receipts natively through the Model Context Protocol.
- Set up the MCP server -- run PEAC as an MCP tool provider
- Explore agent protocol mappings -- how PEAC maps to MCP, ACP, TAP, and UCP
- Install packages -- add the MCP mapping layer
Key packages: @peac/mcp-server, @peac/mappings-mcp
Payment evidence
You want to attach payment proof to receipts for commerce and billing workflows.
PEAC supports multiple payment rails. Each adapter normalizes payment processor events into standard receipt evidence that verifiers can validate.
- Choose your payment rail -- x402, Stripe, card networks, or generic HTTP 402
- Run the quickstart -- understand basic receipt issuance first
- Install rail packages -- add the adapter for your processor
Key packages: @peac/rails-x402, @peac/rails-stripe, @peac/rails-card, @peac/pay402
Compliance and security
You want to verify evidence, audit agent interactions, or investigate disputes.
PEAC receipts are structured, signed, and independently verifiable. Evidence bundles package everything an auditor needs into a single portable archive.
- Learn verification -- how the 12-check verification pipeline works
- Understand evidence bundles -- portable audit artifacts with manifest and signatures
- Review protocol scope -- the verification domains PEAC covers
- Use the Policy Kit -- deterministic policy evaluation for CAL semantics
Key packages: @peac/protocol, @peac/cli, @peac/audit, @peac/policy-kit
OpenClaw capture
You want to capture interaction evidence using the OpenClaw adapter with durable storage and deduplication.
OpenClaw provides a one-call activate() setup with spool stores, deduplication indexes, and structured export counters.
- Set up OpenClaw capture -- configure the capture pipeline
- Export evidence bundles -- package captured evidence for audits
- Install packages -- add the adapter and storage layers
Key packages: @peac/adapter-openclaw, @peac/capture-core, @peac/capture-node