Add signed records beside the systems you already use.
Your gateway, MCP server, API, runtime, or payment rail keeps doing its job. Originary adds a signed record that can be verified outside that system.
Start with the category that matches your workflow, then use the technical surface map only when you need package-level detail.
Agent and tool workflows: MCP, A2A, managed runtimes, OpenClaw. API and gateway workflows: HTTP APIs, reverse proxies, Gateway 402, Cloudflare/Vercel-style edges. Commerce and payment workflows: x402, paymentauth/MPP, ACP, Stripe-style payment events. Audit and provenance workflows: OpenTelemetry exports, in-toto, SLSA, record bundles.
x402 (HTTP 402)
Priced API access with signed records. PEAC v0.14.0 reads x402 v1 and v2 payment responses, maps offer and receipt evidence, and writes PEAC-Receipt as the verifiable record carrier.
paymentauth / MPP↗
HTTP Payment Authentication and MPP payment-attempt or settlement flows mapped into PEAC evidence. Use it when paymentauth challenges, credentials, receipts, and PEAC records must coexist.
Agent-to-Agent (A2A)
Carry signed interaction records through A2A v1.0.0 metadata so another party can verify authorization and policy handling across agent hops and delegated workflows.
MCP Server
Five MCP tools for verify, inspect, decode, issue, and bundle. PEAC records can travel through MCP _meta while remaining independently verifiable.
AI Preferences (AIPREF)
Machine-readable AI agent policy terms can be declared separately from the signed records that prove what happened under those terms.
Agentic Commerce Protocol (ACP)
ACP delegated commerce sessions mapped into access, session, payment-observation, and capability evidence. ACP state is preserved without treating session evidence as payment finality.
Managed agents↗
Managed-agent evidence across session, task, tool-use, MCP-call, permission, and outcome event families. Runtime governance adds observations from managed agent platforms.
OpenClaw↗
Adapter support for OpenClaw tool calls with a low-latency capture path and background receipt emitter. Inputs and outputs are hashed by default unless explicitly allowlisted.
x402 vertical adapters↗
Daydreams inference routing, Fluora MCP marketplace calls, and Pinata private IPFS objects can all map x402 commerce evidence into PEAC records.
in-toto / SLSA↗
Supply-chain mappings connect PEAC signed records to provenance and attestation workflows without replacing existing build or release systems.
PEAC Protocol↗
The open standard for verifiable interaction records. Policy discovery, signed record format, and deterministic verification.
Technical surface map
Current PEAC source exposes 36 published packages across core verification, commerce mappings, agent runtimes, and record export surfaces.
Core and carriers
- @peac/protocol
- @peac/crypto
- @peac/schema
- @peac/mappings-mcp
- @peac/mappings-a2a
- @peac/mcp-server
Commerce
- @peac/adapter-x402
- @peac/mappings-paymentauth
- MPP mappers
- @peac/mappings-acp
- Stripe-style event mapper
- @peac/pay402
Agent runtimes
- @peac/adapter-openclaw
- @peac/adapter-managed-agents
- @peac/adapter-runtime-governance
- @peac/adapter-openai-compatible
Record exports
- @peac/mappings-intoto
- @peac/mappings-slsa
- @peac/telemetry-otel
- @peac/transport-grpc
Need a custom integration?
We build protocol integrations for enterprises. Contact us to discuss your requirements.
Contact us