Agents cross boundaries.
Logs don't.
When an agent, API, or MCP server acts across systems, each side has its own logs. PEAC adds signed, portable records both sides can verify independently.
Portable signed records for agent, API, MCP, and cross-runtime interactions. No central authority required.
How it works
/.well-known/peac.txtPEAC-Receipt: eyJ...verifyLocal(receipt, key)What you have vs. what PEAC adds
Essential for debugging and operations within your system boundary.
Distributed traces and metrics across your stack. The standard for internal observability.
Signed, portable records that complement logs and traces with cross-boundary verification. No central authority required.
The boundary problem
When systems disagree, there is no neutral record
Provider
“Our API returned the agreed response. Our logs confirm it.”
Operator
“That is not what we received. Our logs tell a different story.”
Auditor
Screenshots. Fragmented traces. No shared artifact both sides can independently verify.
What PEAC provides
A signed record issued at the moment of interaction, verifiable by any party, portable across systems. Both sides hold the same artifact. No central authority arbitrates the truth.
Use cases
What PEAC enables
Governed APIs and agent calls
Publish machine-readable terms and return proof that those exact terms were applied to that exact request. No vendor arbitrates the truth.
MCP tool call evidence
Attach a signed record to every MCP tool response. Agents and operators each hold verifiable proof of what happened.
Audit and dispute resolution
When an action is questioned, present the signed record or export a bundle. Not screenshots and logs from one side.
Complementary by design
The records layer
PEAC works alongside the systems you already use. It does not replace auth, payments, observability, orchestration, or transport protocols. It adds portable signed records across them.
Essential debugging and operational visibility within your system
Distributed traces and metrics: the standard for internal observability
Identity verification and access control for your services
Tool coordination and agent-to-agent communication protocols
Moving funds, settlement, and financial infrastructure
PEAC is the records layer. It complements every system above without replacing any of them.
What PEAC is not
PEAC is intentionally narrow. It is the records layer, not a platform.
Protocol flow
How PEAC works
Publish terms
Service publishes machine-readable access, payment, and usage terms.
/.well-known/peac.txtReturn a signed record
Every response carries a signed interaction record in the header or transport metadata.
PEAC-Receipt: eyJ...Verify locally
Any party verifies the record offline using the issuer's public key.
verifyLocal()Export a bundle
Export a portable archive with records, policy snapshots, keys, and verification output.
peac-bundle/0.1Choose your starting point
Start with one integration path, then expand.
Stewarded by
Open protocol. Public development.
PEAC is an Apache-2.0 protocol project developed in public. Specifications, releases, conformance artifacts, and reference implementations are open. Originary stewards the project during the pre-1.0 phase alongside community contributors.
Common questions
Who is using PEAC today?
PEAC is early-stage but already has a public verifier, CLI, MCP server, TypeScript packages (37 packages), Go support for core verification flows, conformance artifacts (224 conformance IDs), and reference integrations for APIs, MCP, A2A, runtime governance, and commerce-related records.
How long does integration take?
Adding the Express middleware takes under 5 minutes. A full MCP server integration with 5 tools takes about an hour. Integrating a payment rail involves mapping payment events to PEAC commerce evidence fields, which typically takes a day for a new adapter.
What does PEAC cost?
Nothing. PEAC is an Apache-2.0 open standard. There is no hosted service, no account, no API key, and no usage fee. You publish your own keys and policy, sign receipts with your own infrastructure, and verifiers check them independently.
Does PEAC replace our existing logs, traces, or auth?
No. Logs stay local. Traces correlate systems. Auth controls access. PEAC adds a signed record another party can verify independently.
Is verification really offline?
Yes. Once you have the issuer's public key or a bundled verification artifact, signature and claims verification are local.
Is PEAC production-ready?
The interaction record format and verification surface are stable. PEAC is pre-1.0, so some library APIs may still evolve.
Open protocol. Active development.
PEAC is an early-stage open standard. Wire format and verification surface are stable at v0.12.11. Library APIs may still evolve before v1.0.