Short answer: this is not a direct rival. The public wshobson/agents repository describes a multi-harness marketplace for distributing agent plugins, skills, commands, and workflows. Ontario Protocol is the pre-payment trust layer for checking whether a paid x402 endpoint is ready to call before an agent spends.
The wshobson/agents README presents one source of truth for plugins and says the marketplace supports multiple agent harnesses, including Claude Code, Codex CLI, Cursor, OpenCode, Gemini CLI, and GitHub Copilot. Its public quick start focuses on installing plugins and generating harness-native artifacts. The inspected README does not present the repository as an x402 endpoint verifier, payment facilitator, signed readiness-report service, or settlement monitor.
Ontario's public contract is different: discover machine-readable payment metadata, run a free readiness check, inspect the HTTP 402 challenge, apply a can-pay policy gate, and retain a report or evidence receipt before a paid call. Ontario's evidence is point-in-time and does not guarantee future endpoint behavior.
Source checked: the public wshobson/agents README and repository page. Corrections or additions can be sent to hello@ontarioprotocol.com.
| Job | wshobson/agents | Ontario Protocol | What an agent still needs |
|---|---|---|---|
| Distribute agent behavior | Public plugin, skill, command, and workflow marketplace. | Not Ontario's primary job. | Install only from a source the operator trusts; review permissions and provenance. |
| Discover paid endpoints | Repository discovery may help a developer find tools, but the README does not define an x402 service catalog. | Machine-readable x402 manifest, discovery feed, and readiness reports. | Confirm the endpoint, resource, price, network, and freshness match the task. |
| Verify x402 launch readiness | Not stated in the inspected public README. | Free verifier checks manifest, OpenAPI, pricing, 402 behavior, and evidence fields. | Read warnings and remediation; do not treat a report as a permanent certification. |
| Decide before payment | Not stated as a payment-policy function in the inspected public README. | Free can-pay policy preflight returns allow, review, or deny inputs. | Pay only after policy, budget, purpose, asset, network, and challenge checks pass. |
| Retain audit evidence | Repository history provides source provenance for its own artifacts. | Public report IDs and bounded evidence receipts for Ontario checks. | Store the target URL, report ID, quote, payment response, and outcome in the agent's own audit log. |
When a plugin calls a paid endpoint, link the user or agent to Ontario's free verifier and buyer policy. Keep payment signing in the caller's own wallet policy.
curl -X POST https://ontarioprotocol.com/api/verify/x402-readiness \
-H "Content-Type: application/json" \
-d '{"target_url":"https://example.com/api/paid-endpoint"}'
A plugin catalog can tell an agent how to perform a task. Ontario can supply observable evidence about the paid endpoint before that task becomes a payment.
1. Discover the tool and endpoint 2. Verify the x402 endpoint 3. Run /api/agent/can-pay 4. Probe HTTP 402 5. Pay only after policy allow
Ontario should not try to out-market a general plugin repository on plugin count or harness breadth. The sharper wedge is the missing handoff after a tool is discovered: endpoint readiness, payment-challenge evidence, freshness, and an auditable pre-payment decision.