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.
Agent Protocols
Evidence carriers for agent-to-agent communication
MCP
@peac/mappings-mcpAttach verifiable evidence to MCP tool responses via _meta fields.
A2A
@peac/mappings-a2aCarry evidence through A2A metadata in TaskStatus, Message, and Artifact.
ACP
@peac/mappings-acpEvidence carrier via ACP headers with 8 KB size limit.
UCP
@peac/mappings-ucpEvidence in UCP webhook payloads with 64 KB embed limit.
TAP
@peac/mappings-tapTAP token mapping with receipt evidence binding.
AIPREF
@peac/mappings-aiprefIETF AIPREF preference mapping for content use policies.
RSL
@peac/mappings-rslRSL token mapping with policy-aware collective licensing.
Payment Rails
Verifiable evidence for payment flows and billing disputes
x402
@peac/rails-x402Verifiable payment evidence for HTTP 402 flows with crypto and fiat support.
Stripe
@peac/rails-stripeMap payment intents and settlement events into verifiable receipts.
Card
@peac/rails-cardGeneric card payment evidence normalization.
Razorpay
@peac/rails-razorpayRazorpay payment event mapping for billing evidence.
Frameworks
Middleware and edge platform support
AI and Inference
Interaction evidence and content policy observation
Agent Runtimes
Capture evidence from agent execution frameworks
Observability
Bridge receipt events to monitoring infrastructure
Evidence 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.