Protocol adapters for PEAC
Each adapter connects PEAC to one external standard: AIPREF for publisher preferences, x402 for payments, MCP for tool context, C2PA for content provenance. They translate between formats so your code stays protocol-neutral.
Adapter ecosystem
AIPREF Adapter
READYReads AIPREF files (aipref.txt) and maps publisher preferences to PEAC policy fields. Checks training, scraping, and attribution permissions before issuing records.
HTTP 402/x402
READYImplements the x402 payment challenge flow: returns 402 with pricing headers, verifies payment proof, issues a signed PEAC record on success. Works with Stripe and on-chain rails.
MCP Server
READYOpen-source MCP tool server (@peac/mcp-server) with 5 tools: verify, inspect, decode, issue, and bundle. Capability-based access control with structured outputs.
robots.txt/llms.txt
READYParses robots.txt (RFC 9309) and llms.txt files to extract crawl and AI-training directives. Maps discovered rules to PEAC content signal fields.
C2PA Adapter
READYExtracts C2PA content credentials from images and documents, maps provenance claims to PEAC attribution and provenance extension fields.
OpenClaw (Cloudflare)
READYOne-call activate() setup for Cloudflare Workers with @peac/rails-openclaw. Includes generateSigningKey() and peac-keygen CLI for key management.
Custom Adapters
ENTERPRISENeed to connect PEAC to a protocol not listed here? We build custom adapters for proprietary or emerging standards. Contact us with the spec.