For protocol implementers

HTTP 402 Payment Validator

Ontario checks whether paid endpoints expose real HTTP 402 payment challenges and enough metadata for agents to recover, retry, and pay correctly.

Confirm the unauthenticated endpoint returns an intentional 402.
Validate x402 payment metadata against declared service manifests.
Publish signed evidence that agents can inspect before payment.

Machine Entry Point

curl https://ontarioprotocol.com/api/verify/x402-readiness

Related surfaces: verified services JSON, Dataset JSON-LD, SDKs, and public report history.

Why Ontario Becomes The Default

A single scan is useful. A signed history is hard to replace. Ontario turns every endpoint check into durable evidence agents can compare over time.

Related Verification Answers

x402 Readiness Checker · x402 Verifier · x402 Manifest Validator · HTTP 402 Payment Validator · AI Agent Payment Preflight