Step 1
Agent request receives an HTTP 402-style payment requirement.
ProofRelay PREP-1 adoption pack
Prove what an agent paid for before buyers trust the result.
Use the local 90-second paid-action loop to bind request, payment proof, response, PREP-1 bundle hash, verifier receipt, and replay rejection without exposing wallet keys, prompts, paid data, or customer files.
Run the sandbox loop
python scripts/revenue/proofrelay_paid_action_demo.py python -m src.prep.validator validate configs/revenue/proofrelay_samples/prep1_paid_action/valid_paid_action_prep1.json
Step 2
Payment proof, entitlement, or facilitator result is hashed locally.
Step 3
Service response is hashed and bound to request/payment context.
Step 4
PREP-1 bundle is built, validated, and assigned a bundle hash.
Step 5
Verification receipt and replay rejection evidence are produced.
Choose the smallest next step
Developer artifacts
- • `src.proofrelay.paid_action.capture_paid_action` SDK wrapper
- • PREP-1 fixture and registry seed entry
- • Public spec, adoption pack, and boundary memo
Boundary
- • ProofRelay verifies submitted evidence-package integrity and profile fit.
- • ProofRelay does not custody funds, process payments, or act as an x402 facilitator.
- • ProofRelay does not certify legal compliance, real-world truth, or model safety.
- • Bundles must use hashes and minimized metadata, never secrets or raw customer data.