Adapters & Integrations
PEAC provides unified verifiable interaction records across systems and organizational boundaries. One receipt format designed to compose with MCP, ACP, A2A, TAP, UCP, x402, payment gateways, and more via adapters and mappings.
Agent Protocol Mappings
Integrate with AI agent and commerce protocols
MCP
@peac/mappings-mcpModel Context Protocol integration with budget utilities.
- Per-call and daily budget limits
- Bigint minor units for precision
- Tool call authorization
ACP
@peac/mappings-acpAgentic Commerce Protocol for agent-to-agent transactions.
- Budget enforcement utilities
- Agent identity binding
- Multi-hop transaction support
TAP
@peac/mappings-tapVisa Trusted Agent Protocol mapping with signature verification.
- RFC 9421 HTTP Message Signatures
- Time window validation (8 min max)
- Fail-closed security defaults
RSL
@peac/mappings-rslRobots Specification Language alignment for crawl permissions.
- RSL 1.0 token mapping
- Extended ControlPurpose (ai_input, ai_index, search)
- Collective licensing support
UCP
@peac/mappings-ucpGoogle Universal Commerce Protocol webhook verification and mapping.
- Detached JWS verification (RFC 7797)
- UCP order to PEAC receipt mapping
- Dispute evidence generation for audit bundles
- ES256/ES384/ES512 signature support
AIPREF
@peac/mappings-aiprefIETF AIPREF vocabulary mapping for purpose declarations.
- Purpose token normalization
- Canonical purpose mapping
- Robots.txt bridge
A2A
spec: a2a-protocol.orgAgent-to-Agent Protocol integration for agent identity and proof of control.
- Agent Card extension (extensions.org.peacprotocol)
- Key directory discovery patterns
- Proof-of-control binding
Payment Rails
3 adaptersx402
@peac/rails-x402HTTP 402 extension with v2 protocol support and v1 backwards compatibility.
- v2 dialect with automatic v1 fallback
- CAIP-2 network identifiers (Base, Avalanche, Solana)
- Standard HTTP 402 semantics
- Payment header negotiation
Payment gateways
@peac/rails-stripeTraditional payment gateway integration with webhook verification and receipt issuance.
- Checkout Sessions and Payment Intents
- Webhook signature verification
- Subscription billing support
- Receipt issuance on payment success
Card Billing
@peac/rails-cardGeneric card billing bridge with billing_snapshot support.
- billing_snapshot in payment.evidence
- Works with any card processor
- Statement descriptor support
x402 Vendor Adapters
Normalize vendor-specific events to PaymentEvidence
Daydreams
@peac/adapter-x402-daydreamsAI inference router adapter for Daydreams events.
- Event normalization to PaymentEvidence
- Model and token tracking
- Inference cost attribution
Fluora
@peac/adapter-x402-fluoraMCP marketplace adapter for Fluora hosting events.
- Tool call metering
- Hosting cost tracking
- MCP integration
Pinata
@peac/adapter-x402-pinataIPFS gateway adapter for Pinata private objects.
- Private IPFS object access
- Bandwidth tracking
- CID-based authorization
Infrastructure
Low-level utilities and transports
Contracts
@peac/contractsSingle source of truth for error codes and MODE_BEHAVIOR contract.
- Canonical E_* error codes
- WWW-Authenticate builder
- Contract-driven design
Worker Core
@peac/worker-coreRuntime-neutral TAP verification handler with security hardening.
- Default mode: tap_only
- Error message sanitization
- LRU replay protection
HTTP Signatures
@peac/http-signaturesRFC 9421 HTTP Message Signatures parsing and verification.
- Full RFC 9421 compliance
- Signature-Input parsing
- Component extraction
JWKS Cache
@peac/jwks-cacheEdge-safe JWKS fetch with SSRF protection.
- Literal IP blocking
- No redirect following
- Cache TTL management
gRPC Transport
@peac/transport-grpcgRPC transport with HTTP StatusCode parity.
- StatusCode mapping to HTTP
- Streaming support
- Metadata propagation
Observability & Telemetry
Trace correlation and metrics for PEAC operations
OpenTelemetry
@peac/telemetry-otelOpenTelemetry adapter for PEAC telemetry with privacy modes.
- Privacy modes: strict, balanced, custom
- W3C Trace Context support
- Metrics and spans for issue()/verify()
Provenance & Attribution
Content derivation proofs and C2PA bridging
Attribution
@peac/attributionContent derivation and usage proofs for AI training, RAG, and content reuse.
- Content hash verification (SHA-256)
- Attribution chain resolution
- C2PA provenance bridging
Example: Rail-Agnostic Verification
import { verify } from '@peac/protocol'
// Works with any payment rail - same verification logic
app.use('/api/premium', async (req, res, next) => {
const receipt = req.header('PEAC-Receipt')
if (!receipt) {
return res.status(402).json({
type: 'https://www.peacprotocol.org/problems/payment-required',
title: 'Payment Required',
rails: ['x402', 'card', 'payment-gateway']
})
}
const result = await verify(receipt, {
issuerAllowlist: ['https://api.example.com']
})
if (!result.ok) {
return res.status(401).json({ error: result.error.code })
}
// Receipt is valid - rail-agnostic verification
console.log('Rail:', result.claims.payment.rail) // 'x402' | 'card' | ...
console.log('Amount:', result.claims.amt, result.claims.cur)
console.log('Facilitator:', result.claims.payment.facilitator) // 'daydreams' | 'fluora' | ...
next()
})Get Started
Install a payment rail adapter and start issuing verifiable receipts.
# Install core + your preferred rail pnpm add @peac/protocol @peac/rails-x402 # Or for payment gateways pnpm add @peac/protocol @peac/rails-stripe