Proof, not filler

x402 evidence pages

These pages are built from scanner behavior, report history, protocol documentation, and concrete remediation examples. They are the content layer Ontario should expand.

Crawler hit next step

Turn proof-page inspection into a buyer-safe action

If you arrived here from a directory, crawler, or paid-agent endpoint review, start with free evidence before any wallet action: verify the endpoint, run can-pay, then use the paid endpoint only after your policy says allow.

Listing conversion

Checklist: Get Your x402 Service Into /discover

Concrete checklist Ontario verifies before your x402-paid endpoint appears in /discover: HTTP 402 challenge shape, /.well-known/x402.json alignment, OpenAPI, and linkable readiness evidence.

Benchmark proof

Paid API Benchmark Scoring

How Ontario scores x402-paid AI-agent APIs without making paid settlement calls: uptime, x402 correctness, schema quality, price clarity, network clarity, and report history.

Listing remediation

Fix a Pending x402 Listing (Pending → Ready)

Remediation playbook for x402 services stuck in pending/needs_work: make HTTP 402 challenge metadata, /.well-known/x402.json, OpenAPI, and public evidence agree so agents can cite a ready report before paying.

Security research → guardrails

Five Attacks on x402 Agentic Payment Protocol

Free x402 agentic payment protocol attack checklist: test request binding, replay, settlement finality, metadata privacy, and discovery poisoning before an agent pays.

MCP + x402

MCP Paid-Tool Security Checklist

Checklist for MCP tools that expose paid x402 services: schema clarity, output validation, human-in-the-loop controls, payment metadata, and Ontario certification.