PEAC
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.15.0|36 packages · 290 conformance requirements|Apache-2.0

Choose your path

Choose your path

I run an API or HTTP service

Issue signed records proving what happened during API interactions.

1
Installpnpm add @peac/middleware-express @peac/crypto @peac/protocol
2
Follow the API Provider Quickstart
3
See hello-world example
@peac/middleware-express@peac/protocol@peac/crypto

I want to verify a record

Verify a record offline with just a public key.

1
Installpnpm add @peac/protocol @peac/crypto
2
Follow the Agent Operator Quickstart
3
See minimal example
@peac/protocol@peac/crypto

I run an MCP server

Add record operations to your MCP server, or attach verifiable records to tool responses.

1
Try it nownpx -y @peac/mcp-server --help
2
Read the MCP Integration Kit
3
See mcp-tool-call example
@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
2
Read the A2A Integration Kit
3
See a2a-gateway-pattern example
@peac/mappings-a2a@peac/protocol

More paths

More paths

Commerce protocol records

Map x402, paymentauth / MPP, and ACP observations into PEAC records with strict semantic boundaries.

@peac/mappings-paymentauth@peac/mappings-acp@peac/adapter-x402

Managed runtime records

Record governed runtime decisions and export them across boundaries.

@peac/adapter-runtime-governance

Verify and bundle

Verify locally, then export a bundle for audit, dispute, or review.

@peac/protocol@peac/audit

Foundation

Core Concepts

Record
A signed JWS (interaction-record+jwt) that proves what happened during an observed interaction
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 (19 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.

Verify a sample recordReference quickstartDocumentation