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.
These pages are built from scanner behavior, report history, protocol documentation, and concrete remediation examples. They are the content layer Ontario should expand.
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.
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.
Fix five x402 implementation mistakes before agents pay: missing accepts, network mismatch, stale manifests, invalid prices, and facilitator gaps.
A concrete before/after example showing how a broken x402 manifest becomes agent-readable and payment-ready.
Current x402 endpoint readiness benchmark using signed reports, service profiles, freshness, certification status, and score history.
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.
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.
Free x402 agentic payment protocol attack checklist: test request binding, replay, settlement finality, metadata privacy, and discovery poisoning before an agent pays.
Checklist for MCP tools that expose paid x402 services: schema clarity, output validation, human-in-the-loop controls, payment metadata, and Ontario certification.