Generate the workflow
The workflow checks the public endpoint at CI time. It does not expose repository contents to Ontario, sign payments, or prove endpoint safety.
Fail CI before your x402 endpoint asks agents to pay.
Generate a self-contained GitHub Actions workflow that calls Ontario's free readiness API, prints the public report link, and fails the job when the endpoint is below the default readiness threshold. Commit it to your own repository; no third-party Action, wallet, API key, or payment is required.
Copy into .github/workflows/ontario-x402-readiness.yml
Enter your public endpoint and generate the workflow.
What it gates
HTTP 402 behavior, payment metadata, manifest/OpenAPI evidence, price/network consistency, and the current readiness grade returned by the public verifier.
What it creates
A report URL in the GitHub Actions summary and a failed job when the endpoint is not ready. Your team controls the merge and deployment decision.
What it cannot prove
A passing CI check is not a security audit, settlement guarantee, ranking signal, traffic promise, or proof of future endpoint behavior.
After the free workflow
If the report shows a rail, metadata, or discovery decision your team does not want to resolve alone, use the $99 rail-fit memo. If the endpoint needs catalog, MCP, README, or registry implementation work, use the qualified $199 launch pack. If you operate several endpoints, request the $99/month Readiness Watch pilot.