Utility guide

Prove what an agent paid for without exposing the private result.

Use hashes, entitlement context, receipt IDs, and replay checks to show what was requested, delivered, and verified around a paid MCP/API action.

Try the $49 Developer Bundle Run the replay demo

Minimal evidence shape

tool_call_hash: sha256...
result_hash: sha256...
payment_context_hash: sha256...
entitlement_hash: sha256...
receipt_id: paid_tool:example.lookup:1780000002000

When to use this

• A buyer or agent pays for a tool result and needs a portable proof artifact.
• A marketplace listing needs to show paid-tool response integrity without leaking paid data.
• A dispute reviewer needs receipt hashes and entitlement context instead of raw logs.

Template

{
  "tool_call_hash": "sha256...",
  "result_hash": "sha256...",
  "payment_context_hash": "sha256...",
  "entitlement_hash": "sha256...",
  "receipt_id": "paid_tool:example.lookup:1780000002000"
}

Local demo commands

python3 scripts/revenue/proofrelay_cli.py paid-receipt-demo

python3 scripts/revenue/proofrelay_cli.py replay-demo

Boundary

ProofRelay verifies internal evidence consistency, receipt ordering, payment or entitlement context, hash-chain continuity, and replay behavior for submitted non-confidential bundles.

ProofRelay does not process payments, custody funds, settle x402 charges, certify legal/title status, verify real-world truth, review source code, or certify model safety.

ProofRelay offer ladder

PREP-1 sandbox offer $5 single verification $49 developer bundle $500 verification credit pack $2,500 workflow assessment