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.
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.
Common x402 Implementation Mistakes
Concrete x402 implementation mistakes Ontario checks before agents pay: missing accepts entries, network mismatch, stale manifests, invalid prices, and facilitator metadata gaps.
Before/After: Fixing A Broken x402 Manifest
A concrete before/after example showing how a broken x402 manifest becomes agent-readable and payment-ready.
Live x402 Endpoint Readiness Benchmark
Current Ontario readiness benchmark using signed reports, service profiles, certification status, and score history.
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.
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.
Threat Model: x402 Agentic Payment Attacks + Preflight Mitigations
Evidence-first checklist for x402 agentic payment risks: requirement tampering, replay/idempotency failures, settlement latency games, PII leakage in metadata, and discovery poisoning. Includes pre-payment mitigations Ontario encourages agents to enforce.
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.