PEAC Protocol produces signed interaction receipts and dispute bundles around agent tool calls and API settlements — overlapping vocabulary (evidence, MCP, x402) with a different object of proof. DocImprint signs what was captured from a PDF or URL and proves which passages support each claim.
Not a drop-in replace. DocImprint is not a PEAC replacement for interaction / settlement receipts. Same words (“evidence bundle”); different job — document capture + citations vs tool-call accountability.
PDF/URL → signed manifest with artifacts (screenshot, PDF, Markdown, OCR) Merkle proofs for quoted citations, not only receipt inclusion Legal hold, retention, and optional Base notarization for high-trust documents
| Capability | PEAC | DocImprint |
|---|---|---|
| Primary object | Interaction / payment receipts | Document evidence bundles |
| Document extract + claim-check | No | Yes |
| Offline-verifiable packages | Yes | Yes (ZIP + keys) |
| MCP | Yes | Yes |
| x402-aware flows | Yes | Yes (pay-per-extract) |
| Paragraph citation Merkle proofs | No | Yes |
Both talk about evidence bundles, offline verify, MCP, and sometimes x402. PEAC attests agent interactions; DocImprint attests document captures and cited answers.
When you need cryptographic proof of tool calls, policy decisions, or payment disputes — not when you need to prove what a PDF or URL contained.
More comparisons: vs LlamaParse · vs Firecrawl · vs Unstructured · vs Lido · vs VerifiedState