Readiness history
Keep point-in-time reports for up to five public endpoints so a team can compare score, grade, warnings, and freshness instead of relying on a launch-day screenshot.
A passing launch check can become stale when price, network, manifest, OpenAPI, payment challenge, or facilitator metadata changes. Readiness Watch is a qualified pilot for teams that need recurring evidence and configured drift alerts before agents keep relying on an old report.
Keep point-in-time reports for up to five public endpoints so a team can compare score, grade, warnings, and freshness instead of relying on a launch-day screenshot.
Review changes to HTTP 402 behavior, accepts entries, price, asset, network, resource URL, and facilitator metadata before agents encounter a contradiction.
Track public manifest, OpenAPI, service profile, and catalog-facing metadata changes that can make an endpoint less legible to agents and registries.
Confirm the intended email or webhook recipient and alert threshold during qualification. Alert delivery is part of the pilot scope, not an unverified public promise.
Run the live verifier or commit the free CI workflow so the initial endpoint scope is concrete.
Provide up to five public endpoints, preferred cadence, alert destination, and the fields that should trigger review.
Ontario confirms the scan schedule, storage, alert path, report retention, and billing route before any invoice is issued.
Use the report history as operational evidence. Re-check the endpoint and payment policy before material spend.
Agents and teams need current evidence when an endpoint changes. Monitoring is valuable only when the schedule, alert delivery, retention, and thresholds are actually agreed and working.
Ontario does not guarantee endpoint safety, service quality, settlement success, uptime, traffic, ranking, revenue, legal compliance, or future behavior. This public page does not promise an SLA.
Readiness Watch pilot