When Not to Use PEAC
PEAC is a signed evidence layer for automated interactions. It is not a general-purpose infrastructure tool.
Right tool for the job
When PEAC is the right tool
- Signed, portable evidence of what happened during an automated interaction
- Offline verification without contacting the issuer
- Evidence that crosses organizational boundaries
- Structured claims with typed extensions (commerce, consent, identity)
- A neutral evidence layer across MCP, A2A, x402, ACP, gRPC, and HTTP
Complementary tools
When other tools are a better fit
Internal logging is sufficient
All parties are within the same trust boundary. Standard logging, APM, or SIEM is simpler. PEAC is for evidence that crosses organizational boundaries.
You need a payment rail
PEAC records evidence of payment interactions. It does not move money, authorize transactions, or settle payments.
You need agent messaging
PEAC does not route messages, coordinate tasks, or manage agent lifecycles. It carries evidence alongside agent protocols.
You need policy evaluation
PEAC records what terms applied. It does not evaluate or enforce policies.
You need real-time observability
Receipts are signed artifacts created after an interaction completes. Not designed for real-time monitoring or streaming telemetry.
You need identity management
PEAC does not issue or manage identities. It uses existing identity systems (Ed25519 keys, DIDs, JWKS) to sign and verify.
You need a trust score
PEAC provides raw, verifiable evidence. It does not compute trust scores or reputation metrics. Evidence can serve as input to a reputation system.
A simpler format is enough
If you need only a signed timestamp or simple attestation without structured claims, a plain JWS may suffice.
PEAC fits your use case?
Pick an integration path and issue your first signed receipt in minutes.