Public verification report

x402 readiness evidence report

https://ontarioprotocol.com/api/agent/pay/v2

ready

Report vrf_c8d0751508c87650, verified at 2026-07-14T10:46:27.823344+00:00 by ontario.x402-readiness.v1. Base score 100/100, warning penalty -15.

85/100

Certification Decision

ready

This is a point-in-time evidence asset. Ontario Certified x402 requires repeated signed reports, integrity-valid history, and fresh readiness evidence before agents should treat the endpoint as an allow candidate.

Evidence Asset

Score85/100 with grade ready
Warnings2 implementation warnings
Remediation0 recommended fixes
Signals15 scanner signals
Integritysigned report available
Machine API/api/verify/reports/vrf_c8d0751508c87650

Report Methodology (How To Read This)

This report is point-in-time readiness evidence produced by ontario.x402-readiness.v1 at 2026-07-14T10:46:27.823344+00:00. It is designed for pre-payment checks (before an agent spends), not as a blanket safety guarantee.

Score model Base score is a weighted sum of observed checks (transport, reachability, 402 challenge, x402 manifest, OpenAPI, and discovery metadata). Warning penalties subtract points for common integration gaps. Final score is clamped to 0–100.
Grade thresholds ready ≥ 85 · close ≥ 65 · needs work < 65.
What it checks HTTPS, homepage reachability, endpoint reachability, HTTP 402 payment challenge, /.well-known/x402.json presence/shape, OpenAPI availability, Bazaar-style listing metadata, robots.txt, and basic schema.org presence.

Not checked: service security, authorization correctness, privacy posture, business logic correctness, load/performance, long-term uptime, or settlement finality. Agents should enforce budgets, policies, and re-verify on a schedule. See the Ontario Trust Standard at /trust.

Trust Boundary

Ontario Protocol provides readiness and trust signals based on observable endpoint behavior, manifest metadata, payment challenge behavior, report history, and public evidence. It does not guarantee endpoint safety, service quality, financial outcome, or future behavior. Agents should re-verify on a schedule and enforce budget, policy review, and independent verification before spending.

Signals

accepts entries
bazaar metadata
endpoint reachable
facilitator metadata
homepage reachable
https
manifest fresh
network consistent
openapi schema
payment challenge
price format valid
robots present
schema org present
x402 manifest present
x402 manifest well formed

Implementation Warnings

Publish facilitator and settlement metadata

Expose facilitator details plus asset, payTo, scheme, timeout, and resource fields so clients can verify and settle payments deterministically. Fix guide

Use machine-parseable x402 price fields

Declare price_atomic as a non-negative integer and price_usdc as a decimal string; keep maxAmountRequired consistent with the advertised service price. Fix guide

Recommendations

No critical fixes found.

Turn this report into a launch decision

This report has 2 implementation warnings. Request one free repair note, the $49 Verified Repair Memo, or scope the fixed-price Agent Catalog Launch Pack if the endpoint is launch-critical.

Want the single highest-impact fix?

Request one free, report-bound repair note. No wallet credentials, payment, or automatic publication is involved.

Machine-readable

curl https://ontarioprotocol.com/api/verify/reports/vrf_c8d0751508c87650

Signed by ontario-protocol using Ed25519. Key: ed25519:67e5239d2bfa367d.

curl https://ontarioprotocol.com/api/verify/reports/vrf_c8d0751508c87650/integrity
curl https://ontarioprotocol.com/api/verify/reports/vrf_c8d0751508c87650/sla

Badge: x402 verification badge

<a href="https://ontarioprotocol.com/verify/report/vrf_c8d0751508c87650"><img src="https://ontarioprotocol.com/verify/report/vrf_c8d0751508c87650.svg" alt="Ontario x402 verification"></a>