Public verification report

x402 readiness evidence report

https://the402.tateprograms.com/api/x402/skill-trust-check

ready

Report vrf_0507322e44a2d099, verified at 2026-05-21T02:41:04.579153+00:00 by ontario.x402-readiness.v1. Base score 95/100, warning penalty -8.

87/100

Certification Decision

Ready

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.

90/100latest score

2ready reports

validsignature integrity

323.36hreport age

3total reports

reviewagent policy hint

Evidence Asset

Score87/100 with grade ready

Warnings2 implementation warnings

Remediation1 recommended fixes

Signals15 scanner signals

Integritysigned report available

Machine API/api/verify/reports/vrf_0507322e44a2d099

Report Methodology (How To Read This)

This report is point-in-time readiness evidence produced by ontario.x402-readiness.v1 at 2026-05-21T02:41:04.579153+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

Refresh the x402 manifest timestamp

A stale or missing manifest timestamp makes agents doubt whether prices, networks, and facilitator metadata still describe the live endpoint. Fix guide

Recommendations

Add listing metadata for Bazaar-style catalogs

Name, description, category, tags, owner URL, and contact fields make services usable in agent marketplaces. Reference

Machine-readable

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

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

curl https://ontarioprotocol.com/api/verify/reports/vrf_0507322e44a2d099/integrity

curl https://ontarioprotocol.com/api/verify/reports/vrf_0507322e44a2d099/sla

Service profile: the402-tateprograms-com-api-x402-skill-trust-check-bab0181c · Ready

curl https://ontarioprotocol.com/api/verify/services/the402-tateprograms-com-api-x402-skill-trust-check-bab0181c

Badge: x402 verification badge

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