Integrations
PEAC provides portable signed proof across agent protocols, payment rails, HTTP frameworks, and AI inference APIs. Each integration maps evidence into or out of a transport-specific format via the Evidence Carrier Contract.
Start Here
Production-ready integrations with full Interaction Record format support
Express / API
Express.js Middleware
@peac/middleware-expressAuto-issue signed receipts on Express.js API responses in 3 lines. A direct path to verifiable evidence on any HTTP API.
MCP
Model Context Protocol
@peac/mappings-mcpAttach verifiable evidence to MCP tool responses via _meta fields. Production-grade carrier with full Interaction Record format support.
x402
HTTP 402 Payment Evidence
@peac/rails-x402Verifiable payment evidence for HTTP 402 flows with v1/v2 dual-header read and upstream artifact separation.
Stable
Verified integrations across protocols, payment rails, standards, and observability
A2A
@peac/mappings-a2aCarry evidence through A2A metadata in TaskStatus, Message, and Artifact. A2A v1.0.0 compatible with dual-version transition support.
Stripe
@peac/rails-stripePayment intent observation and SPT delegation evidence with explicit payment state requirement.
Content Signals
@peac/mappings-content-signalsObserve content use policy signals from robots.txt, AIPREF, and tdmrep.json.
ACP
@peac/mappings-acpSession lifecycle and payment observation evidence with strict semantic boundary.
UCP
@peac/mappings-ucpWebhook verification (RFC 9421 + RFC 9530), order-to-receipt mapping, and dispute evidence.
Card
@peac/rails-cardGeneric card payment evidence normalization.
Razorpay
@peac/rails-razorpayRazorpay payment event mapping for billing evidence.
TAP
@peac/mappings-tapVerify Visa TAP proofs and map them to interaction evidence with a strict issuer trust boundary.
AIPREF
@peac/mappings-aiprefIETF AIPREF vocabulary and Content-Usage header mapping to canonical control purposes.
RSL
@peac/mappings-rslRSL 1.0 usage token mapping to PEAC control purposes for content licensing evidence.
Cloudflare Workers
@peac/worker-coreEdge-compatible receipt verification for Cloudflare Workers.
OpenTelemetry
@peac/telemetry-otelBridge PEAC receipt events to OTel spans and metrics with privacy modes.
Reference Implementation
Working examples that demonstrate evidence patterns for specific domains
Inference
@peac/adapter-openai-compatibleHash-first interaction evidence for chat completion APIs. No raw text stored.
OpenClaw
@peac/adapter-openclawCapture signed interaction evidence from agent tool calls with two-stage pipeline.
Paymentauth
@peac/mappings-paymentauthEnvelope-first HTTP Payment scheme parsing with carrier coexistence and JSON-RPC/MCP helpers.
Browse by record category
Integrations map evidence into and out of transports. If you are looking for what PEAC records, browse the six interaction surfaces: API calls, MCP tool runs, agent actions, gateway decisions, payment events, and provisioning events.
Record CategoriesEvidence Carrier Contract
All integrations share a common interface: the PeacEvidenceCarrier type and CarrierAdapter pattern. This ensures receipts travel across MCP, A2A, ACP, UCP, x402, and HTTP transports without coupling to any single protocol.