Public verification report

x402 readiness evidence report

https://ontarioprotocol.com/api/x402/implementation-audit

close

Report vrf_83da357725384e16, verified at 2026-07-13T21:02:38.405540+00:00 by ontario.x402-readiness.v1.

80/100

Certification Decision

Not certified

Certification is derived from signed report integrity, latest grade, latest score, readiness history, and report freshness. This page is the evidence record behind the badge, not a standalone marketing claim.

/100latest score
ready reports
validsignature integrity
hreport age
25total reports
deny_or_reviewagent policy hint

Evidence Asset

Score80/100 with grade close
Warnings0 implementation warnings
Remediation1 recommended fixes
Signals15 scanner signals
Integritysigned report available
Machine API/api/verify/reports/vrf_83da357725384e16

Report Methodology (How To Read This)

This report is point-in-time readiness evidence produced by ontario.x402-readiness.v1 at 2026-07-13T21:02:38.405540+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

No implementation warnings found.

Recommendations

Expose a real HTTP 402 payment challenge

A paid endpoint should reply with HTTP 402 and a payment requirements header when called without payment. Reference

Turn this report into a launch decision

This report is evidence for one endpoint at one point in time. If you are preparing a registry launch or an agent payment workflow, Ontario can scope the next implementation step without asking for wallet credentials.

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_83da357725384e16

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

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

Service profile: ontarioprotocol-com-api-x402-implementation-audit-3aefce06 · Not certified

curl https://ontarioprotocol.com/api/verify/services/ontarioprotocol-com-api-x402-implementation-audit-3aefce06

Badge: x402 verification badge

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