Skip to content
Integration guide

Start Here

PEAC is most useful when local logs are not enough: cross-boundary verification, audit trails, dispute review, multi-agent workflows, managed runtime exports, and commerce-related records.

v0.12.11|37 packages · 224 conformance IDs|Apache-2.0

Choose your path

Choose your path

I run an API or HTTP service

Issue signed receipts proving what terms applied and what happened.

1
Installpnpm add @peac/middleware-express @peac/crypto @peac/protocol
@peac/middleware-express@peac/protocol@peac/crypto

I want to verify a receipt

Verify a receipt offline with just a public key.

1
Installpnpm add @peac/protocol @peac/crypto
@peac/protocol@peac/crypto

I run an MCP server

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

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

I build A2A agents

Carry receipts across Agent-to-Agent Protocol flows.

1
Installpnpm add @peac/mappings-a2a @peac/protocol @peac/crypto
@peac/mappings-a2a@peac/protocol

Foundation

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

Ready to add verifiable records?

Each path takes under 5 minutes to first receipt. Pick one above, or explore the full documentation.