{
  "markdown": "# Ontario Protocol\n\nFind out why an agent cannot discover or call your x402 API, then publish the\nevidence a buyer needs to evaluate it.\n\n[Run the free buyer-discovery audit](https://ontarioprotocol.com/tools/coinbase-bazaar-readiness?utm_source=github&utm_medium=readme&utm_campaign=provider_launch)\n| [Provider quickstart](https://ontarioprotocol.com/docs/x402-service-listing-quickstart?utm_source=github&utm_medium=readme&utm_campaign=provider_launch)\n| [Inspect current tools](https://ontarioprotocol.com/.well-known/mcp.json)\n\n## Install in your agent\n\nFor API providers preparing a launch:\n\n```bash\nnpx skills add TheTechDevPro/ontario-protocol --skill ontario-provider-launch\n```\n\nFor agent builders checking an endpoint before spending:\n\n```bash\nnpx skills add TheTechDevPro/ontario-protocol --skill ontario-x402-preflight\n```\n\nOr install both from the [Ontario x402 Toolkit pack](https://skills.sh/p/1i9kLVcmDbP4Zbhz):\n\n```bash\nnpx skills add https://skills.sh/p/1i9kLVcmDbP4Zbhz\n```\n\nThe pack is a public, unlisted snapshot of these two skills, published September 6,\n2026. It is not a leaderboard placement, endorsement, or security certification.\n\nSkills contain inspectable instructions. Installation does not create a wallet,\nauthorize a purchase, or change spending limits.\n\n## Connect\n\nThe remote uses Streamable HTTP. No Ontario API key is required for free tools.\nFor clients using `mcpServers`, including Claude Code's `.mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"ontario-protocol\": {\n      \"type\": \"http\",\n      \"url\": \"https://ontarioprotocol.com/mcp\"\n    }\n  }\n}\n```\n\nFor VS Code, see [examples/vscode-mcp.json](examples/vscode-mcp.json). The\n[official Registry record](https://registry.modelcontextprotocol.io/v0.1/servers/com.ontarioprotocol%2Fontario-protocol/versions/latest)\nand [Smithery listing](https://smithery.ai/servers/thom899g/ontario-protocol)\npoint to the same remote. A connected MCP host still needs a compatible local\nx402 wallet and explicit spend policy to use paid tools.\n\n## Try a useful task\n\n> Check whether my public x402 API appears in Bazaar for \"return a sourced\n> company filing\". Report observable blockers. Do not spend or publish anything.\n\nOr call the free HTTP diagnostic directly:\n\n```bash\ncurl --fail-with-body --silent --show-error \\\n  https://ontarioprotocol.com/api/tools/coinbase-bazaar-readiness \\\n  -H 'Content-Type: application/json' \\\n  -d '{\"target_url\":\"https://example.com/api/paid\",\"buyer_query\":\"return a sourced company filing\"}'\n```\n\nReplace the example URL with your own public API. The result separates indexing\npreflight from sampled buyer-query retrieval, with evidence and timestamps.\nIt does not initiate a settlement or submit your service to another registry.\n\n## Free checks and the paid deliverable\n\n| Job | Tool or endpoint | Cost |\n| --- | --- | --- |\n| Diagnose retrieval across five buyer queries | `bazaar_buyer_intent_gap` | Free |\n| Inspect x402 endpoint readiness | `x402_readiness_verify` | Free |\n| Decide whether a proposed spend passes policy | `agent_can_pay` | Free |\n| Find task-relevant paid API candidates | `find_x402_tool` | Free |\n| Validate provider publication inputs | `ontario_validate-service` | Free |\n| Publish a signed provider launch profile | `ontario_list-service` | 0.50 USDC on Base |\n\nThe optional publication includes a canonical HTML/JSON profile, readiness\nevidence, a point-in-time Bazaar retrieval snapshot, a badge, and 30 days of\nincluded automatic freshness maintenance. Providers with an MCP server can add\nMCP Registry and read-only remote-contract evidence to the same purchase.\n\n**Publication does not buy Coinbase or MCP Registry placement, ranking,\ntraffic, customers, a better grade, or a safety guarantee.** Use the free\ndiagnostic first. The paid route returns HTTP 402 before payment. A challenge\nis not a receipt; sign locally only under the owner's policy.\n\n## Publish from your agent without a browser\n\n1. Call `ontario_validate-service` with your public service name, description,\n   endpoint and its per-call price. Fix the returned field errors for free.\n2. Run the free readiness and can-pay checks. Choose publication only when you\n   need the public profile and approve Ontario's separate 0.50 USDC fee.\n3. Call `ontario_list-service` without payment and inspect the live requirements.\n4. A compatible wallet client signs locally and retries with the PaymentPayload\n   in `params._meta[\"x402/payment\"]`. Store the profile and\n   `result._meta[\"x402/payment-response\"]` receipt after success.\n\nOntario supports the [standard x402 MCP payment format](https://docs.cdp.coinbase.com/x402/buyer/mcp-payments).\nThe unpaid MCP result uses HTTP 200 with `isError: true` and `PaymentRequired`\nin both structured content and JSON text. It is not a failed server or a sale.\nThe older `_x402_payment` argument still works. HTTP-wrapper clients can send\n`X-Ontario-X402-Transport: http` for HTTP 402 signaling and retry with\n`PAYMENT-SIGNATURE`. No installation or free check authorizes a payment.\n\nSource labels, when available, are coarse client-reported hints. They do not\nidentify a person or prove a marketplace referred a paying customer.\n\n## Typed responses and compatibility\n\nAll nine tools in the default catalog declare output schemas, documented input\nparameters, and side-effect annotations. Clients can validate successful\nstructured results instead of inferring their shape from prose. The free launch\nkit returns drafts only; optional live verification can create a public report;\npaid publication and evidence refresh remain state-changing operations.\n\nThe September 5, 2026 Smithery refresh reports 98/100, with complete schema,\ndescription, parameter, annotation, metadata, and configuration coverage. Its\nremaining deduction is for flat tool names. Existing names and payment contracts\nare retained for compatibility. This is a listing-quality measure, not a security\naudit, certification, or evidence of customer demand.\n\n## Public distribution check\n\nOn September 5, 2026, an explicitly approved, owner-funded 0.50 USDC activation\nsettled and the exact `/api/x402/list-service` resource appeared in CDP Bazaar and\nAgentic Market. Smithery's original listing was refreshed to the current nine\ntools. The [operator disclosure and transaction receipt](https://ontarioprotocol.com/static/receipts/bazaar-activation-20260905.json)\nmake the test independently inspectable. This was distribution setup, not a new\ncustomer, independent revenue, a security certification, or guaranteed traffic.\n\n## Additional catalog entries\n\n- [Ontario on x402scan](https://www.x402scan.com/server/a2237d73-7805-4004-a4c8-5348f4175312)\n  exposes 21 resources in the public catalog, checked September 6, 2026.\n- [Ontario's Agent402 seller record](https://agent402.tools/api/index?seller=ontarioprotocol.com)\n  exposes 20 tools, including eight paid tools. On September 6, 2026, it reported\n  `routable: true` for crawl readiness but `routerDispatchEligible: false` with\n  `routerDispatchReason: settlement_required`. Its paid router's settlement-history\n  threshold is a separate gate; a successful registration does not satisfy it.\n\nCatalog presence is not an endorsement, a paid call, or evidence of customer\ntraffic. Check each hub's current eligibility before relying on it. The direct\nMCP connection and GitHub skill installation above do not depend on these hubs'\nrouting eligibility. Free checks never authorize a purchase; paid calls still\nrequire a compatible wallet and the owner's spending policy.\n\n## Machine-readable entry points\n\n- [MCP descriptor](https://ontarioprotocol.com/.well-known/mcp.json)\n- [x402 manifest](https://ontarioprotocol.com/.well-known/x402.json)\n- [Agent buyer guide](https://ontarioprotocol.com/.well-known/agent-buyer.json)\n- [Agent payment policy](https://ontarioprotocol.com/.well-known/agent-payment-policy.json)\n- [Agent discovery guide](https://ontarioprotocol.com/docs/x402-agent-discovery)\n\n## Private review handoffs for teams\n\n[Ontario Private Agent Handoff](https://ontarioprotocol.com/services/private-agent-handoff)\nis a free self-service kit for teams operating lead-to-reviewer workflows.\nThe [local Python kit](private-agent-handoff/README.md) signs and encrypts selected\nbrief fields, checks a pinned recipient, expiry, replay and local revocation, and\nreturns a payload-free signed acceptance receipt. It makes no network calls and\ndoes not execute tools or pay. Keep your own authenticated transport.\n\nThe public page includes a rule-based setup assistant, a complete guide, expected\nresults, troubleshooting and a synthetic policy simulator. The assistant adapts\nto the customer's environment without uploading choices, keys or task data.\nUnsupported deployments are not marked ready. Run `demo.py` locally for real encryption,\nreceipt verification and a replay-denial check. No account, wallet, application,\ninvoice or setup call is needed. Guided implementation is no longer offered.\nNo hosted messaging, independent security audit or certification is claimed.\n\nThe local kit is not an MCP tool in the public Ontario server: confidential briefs\nand private keys must never be sent to that server. Read the kit's threat model\nbefore using real data. Existing paid provider publication remains unchanged.\n\n## Trust boundary\n\nOntario provides readiness and trust signals based on observable endpoint\nbehavior, manifest metadata, payment challenge behavior, report history, and\npublic evidence. It does not guarantee endpoint safety, service quality,\nfinancial outcome, or future behavior.\n\nThis repository contains public integration artifacts and skills, not the\nproduction backend or its credentials. Contact: hello@ontarioprotocol.com.\nSecurity reports: security@ontarioprotocol.com.\n",
  "bytes": 9773,
  "sha": "46dedec256b348bd95b4f4c6469de299a6a4936c52a33eaf5366aa3bb7627201",
  "repo_slug": "thetechdevpro/ontario-protocol",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_ontarioprotocol_ontario_protocol_63af9734/readme"
}