Ontario Protocol.
Verification workflow

x402 Payment Verification Tool

Use this workflow when a paid endpoint claims x402 support. It links the free readiness checker, report ledger, trust standard, and can-pay API into one repeatable verification path.

x402 payment verification tool Developers and agent operators validating x402 endpoints before integration.
Open checker UI Call verifier API

Run the workflow

Start with a readiness scan, then use the report output to make an explicit policy decision before an agent signs a payment.

  • Submit the endpoint URL to `/api/verify/x402-readiness`.
  • Save or inspect the generated public report.
  • Call `/api/agent/can-pay` with the agent's policy and max spend.

What the tool catches

The workflow catches missing 402 challenges, malformed payment metadata, manifest drift, stale service metadata, OpenAPI gaps, and report integrity failures.

  • Payment challenge and accepts metadata compatibility.
  • Network, asset, amount, nonce, and expiry consistency.
  • Human and machine-readable proof that agents can cite.

Workflow

Paste a paid endpoint into the checker.
Review readiness score, grade, warnings, and recommendations.
Share the report URL with integrators or buyers.
Use can-pay for automated agent policy enforcement.
Subscribe to alerts if the endpoint becomes business-critical.

Use these Ontario routes to move from content research into live verification evidence.

Checker UI Can-pay API x402 docs