PEAC
Complementary by design

PEAC vs Existing Systems

PEAC is an evidence layer. It complements your existing stack rather than replacing any part of it.

Keep your auth. Keep your payments. Keep your observability. Add /.well-known/peac.txt and return PEAC-Receipt on governed responses.

System by system

How PEAC fits alongside every layer

Application logsComplement

Record what happened inside your system

Logs stay inside your boundary. PEAC receipts cross boundaries and are independently verifiable by the other party.
OpenTelemetryComplement

Distributed tracing, metrics, and observability

OTel traces are observability data. PEAC receipts are signed evidence that correlates to traces but can be verified offline by external parties.
MCP (Model Context Protocol)Complement

Agent-to-tool communication standard

MCP handles tool discovery and invocation. PEAC adds signed evidence to MCP tool responses via _meta fields, proving what happened during the call.
A2A (Agent-to-Agent Protocol)Complement

Agent task delegation and coordination

A2A handles task routing and state. PEAC carries verifiable evidence in A2A task metadata, proving what terms applied across agent boundaries.
x402 (Payment-Required HTTP)Complement

HTTP payment challenges and settlement

x402 handles the payment flow. PEAC maps x402 offers and receipts into verifiable evidence records with offline verification.
Stripe / Payment railsComplement

Transaction processing and settlement

Payment rails move money. PEAC records verifiable evidence of what was authorized, settled, or disputed, without executing payments.
ACP (Agentic Commerce Protocol)Complement

Agent commerce sessions and checkout

ACP manages commerce sessions. PEAC records session lifecycle events and payment observations as portable, verifiable evidence.
OPA / Rego / CedarComplement

Policy evaluation and authorization

Policy engines decide what is allowed. PEAC records what policy was in effect when a decision was made, using policy binding (JCS + SHA-256).
robots.txt / AIPREFComplement

Crawl permissions and content usage signals

These express intent. PEAC records three-state observations of what signals were present and what the crawler did in response.
DIDs / Verifiable CredentialsCompatible

Decentralized identity and claims

PEAC uses DIDs as issuer identifiers (did:key, did:web). Receipts are not VCs but can reference VC-based identity proofs in extensions.
ERC-8004 / On-chain reputationCompatible

Agent reputation scoring

Reputation systems score agents. PEAC receipts serve as raw, verifiable evidence that feeds into reputation calculations.

PEAC is the evidence layer. It complements every system above without replacing any of them.

The evidence layer

What PEAC adds to your stack

  • Portable proof that survives organizational boundaries
  • Offline verification without contacting the issuer
  • Signed evidence that correlates to traces and logs
  • Cross-boundary proof carried alongside MCP, A2A, x402, ACP, gRPC, and HTTP
  • Policy binding that records what terms were in effect

Ready to add the evidence layer?

PEAC works alongside your existing stack. Pick a starting point and issue your first receipt in minutes.

Get startedWhen not to use PEAC