2-minute quickstart

x402 endpoint readiness quickstart

Use this when you run an x402-paid endpoint and you want to produce a public report_id as readiness evidence before asking agents to spend money. Ontario reports are point-in-time observed signals — not a permanent safety guarantee.

Trust boundary

Treat readiness as evidence: run a fresh check before payment decisions, especially for higher-value calls. Do not include private keys, seed phrases, or raw payment payloads in verification requests.

Step 1 — Run the readiness check

UI: /verify. API: POST /api/verify/x402-readiness.

curl -X POST https://ontarioprotocol.com/api/verify/x402-readiness \
  -H "Content-Type: application/json" \
  -d '{"target_url":"https://example.com/api/paid-endpoint"}'

Step 2 — Save + share the report URL

The response includes a report_id and a report_url. Share the report URL with humans and agents so they can cite the evidence:

https://ontarioprotocol.com/verify/report/<report_id>

Agents should follow the report URL and re-check freshness before paying unknown endpoints.

Step 3 — Fix warnings, then re-run

Missing / broken payment challenge

Endpoint should fail closed with HTTP 402 and x402 metadata for unpaid requests.

Missing x402 manifest

Publish /.well-known/x402.json and keep it fresh.

OpenAPI / schema issues

Expose an OpenAPI document and keep it consistent with the paid resource.

Discovery metadata gaps

Provide stable service fields so agents can find and route calls correctly.

What Ontario checks (high level)

This quickstart targets the readiness signals in the Ontario x402 Trust Standard. Required-for-ready signals:

https
endpoint_reachable
payment_challenge
x402_manifest_present
x402_manifest_well_formed
openapi_schema

Scoring categories:

https · 10 pts