Ontario Protocol

Use this path if you are an agent, directory crawler, or endpoint owner trying to decide whether Ontario is worth a real paid call:
- Confirm the public manifests:

- GET https://ontarioprotocol.com/api/x402/reputation/demo-agent
- Expected: HTTP402payment challenge for0.001 USDCon Base.

- POST https://ontarioprotocol.com/api/agent/can-pay

Current boundary: Ontario has public crawler/developer-tool inspection and a self-funded0.01 USDCrail proof, but no verified customer paid call yet. A valid market signal is an accepted listing, rejection, crawler fetch, endpoint-owner request, paid call, signup, or payment.

Ontario Protocol exposes MCP and x402 tools for verifying paid agent endpoints before agents pay. Start with free readiness and can-pay tools, then use paid trust, reputation, and listing tools only after policy allows.

Start with the cheapest paid proof, then use the free preflight before signing:

curl -i https://ontarioprotocol.com/api/x402/reputation/demo-agent curl -fsSL -X POST https://ontarioprotocol.com/api/agent/can-pay \ -H 'content-type: application/json' \ -d '{"endpoint":"https://ontarioprotocol.com/api/x402/reputation/demo-agent","max_usdc":"0.001","agent_policy":"standard"}'

- GET /api/x402/reputation/demo-agentreturns HTTP402withPayment-Required/X-Payment-Required,quote_id,maxAmountRequired=1000,network=base, andpayTo.
- The response also includes free alternatives: can-pay policy check, readiness verifier, sandbox, MCP endpoint, docs, and mini-check path.
- A paid call should happen only after the agent policy allows USDC-on-Base settlement and the caller can store the quote/payment response for audit.

This package exists to support agent/tool directory review. It is not a separate production deployment, not a payment collector, and not a legal or financial guarantee. Ontario provides observable readiness signals; agents should still enforce their own budget, wallet, timeout, and policy controls before payment.

If you run an MCP or x402 endpoint and found Ontario through a directory, start here before any paid action:

The paidlist-serviceroute is only for owners who want a public Ontario catalog listing after the free checks are useful.

Recent public probes are reaching the paid listing endpoint directly. Treat the first HTTP402as price discovery, not as a reason to sign immediately:
- Validate the listing payload without payment:

- POST https://ontarioprotocol.com/api/x402/list-service/validate

- POST https://ontarioprotocol.com/sandbox/api/x402/list-service

- POST https://ontarioprotocol.com/api/x402/list-service

This keeps crawlers, agent operators, and endpoint owners on the no-spend path until the listing is ready enough to justify a paid catalog submission.

Directory crawlers should inspect the live MCP manifest rather than treating this repository as the server implementation:

curl -fsSL https://ontarioprotocol.com/.well-known/mcp.json curl -fsSL https://ontarioprotocol.com/.well-known/x402.json curl -fsSL https://ontarioprotocol.com/api/demand/stats

The remote MCP endpoint acceptsPOST /mcpfor JSON-RPC MCP calls.GET /mcpreturns HTTP405with a JSON method hint, manifest URL, andLinkdiscovery headers; crawlers should fetch/.well-known/mcp.jsonfor the manifest before posting JSON-RPC.

A real market signal for this distribution test must be one of: accepted listing, listing rejection, directory click, crawler/registry fetch, inbound listing attempt, signup, paid x402 call, or payment. Drafts and local reports do not count.

This repository contains public listing metadata only. It does not contain private source code, secrets, wallets, deployment credentials, or payment keys.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.