Paid ProofRelay intake

Start with the smallest paid proof that can create customer evidence.

The fastest path is not a broad platform demo. It is one verified paid action, one clear receipt, and one reason the buyer would pay again. ProofRelay can create the proof envelope behind the scenes; you do not need to hand-author it before starting.

I am testing an MCP/API integration

Default path for builders who want ProofRelay wrapped around a paid or relied-upon action.

Start the $49 developer bundle

I have one action to wrap

Best when you want one entitlement-backed check without learning bundle internals first.

Buy the $5 verification

I am integrating ProofRelay into a product

Best when an agent workflow needs repeated pass/fail/review receipts and audit hashes.

Buy the $500 credit pack

I need GENESIS to map the workflow

Best for refunds, audits, SLAs, compliance, or counterparty reliance.

Start the assessment path

What to prepare

  • • Workflow name and buyer/user segment
  • • Paid action, MCP/API call, or material decision being verified
  • • Action request/response commitments available today
  • • Refund, audit, SLA, or dispute scenario to defend
  • • Expected volume and whether team retention is needed

Support, terms, and marketplace-safe handoff

AWS Marketplace, Google Cloud Marketplace, and direct buyers should start here, then continue to the smallest paid path that fits the workflow. Use public-safe action metadata only. Do not send secrets, private prompts, raw customer files, raw logs, wallet keys, payment credentials, or source code.

Copy MCP setup firstBack to ProofRelay