Utility guide

Show that a paid API result can be checked and replay abuse can be rejected.

ProofRelay records the evidence shape around request, entitlement, response, and replay outcome so operators can prove the API result was not just a transient log entry.

Buy a $5 Single Verification Start the $49 Developer Bundle

Minimal evidence shape

request_hash: sha256...
api_response_hash: sha256...
entitlement_or_charge_hash: sha256...
first_redeem_status: pass
second_redeem_status: entitlement_replay

When to use this

• A paid API response may be relied on by another agent, workflow, customer, or auditor.
• The API operator needs a deterministic replay rejection story for entitlement use.
• The team needs a public-safe proof point for a paid API integration.

Template

{
  "request_hash": "sha256...",
  "api_response_hash": "sha256...",
  "entitlement_or_charge_hash": "sha256...",
  "replay_key": "stripe_checkout_session:test",
  "expected_replay_error": "entitlement_replay"
}

Local demo commands

python3 scripts/revenue/proofrelay_cli.py replay-demo

python3 scripts/revenue/proofrelay_cli.py paid-receipt-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