An open API service indexing awesome lists of open source software.

https://github.com/thom899g/ontario-protocol-mcp-listing

Public MCP/x402 listing packet for Ontario Protocol: remote MCP, x402 readiness, and endpoint-owner discovery.
https://github.com/thom899g/ontario-protocol-mcp-listing

agent-commerce agent-tools ai-agents base directory mcp paid-api usdc verification x402

Last synced: 21 days ago
JSON representation

Public MCP/x402 listing packet for Ontario Protocol: remote MCP, x402 readiness, and endpoint-owner discovery.

Awesome Lists containing this project

README

          

# Ontario Protocol MCP/x402 Listing Package

Ontario Protocol is an x402 payment preflight and trust surface for autonomous agents. It exposes MCP-compatible discovery, free readiness checks, and paid trust tools so agents can verify service metadata before paying.

Homepage:

MCP manifest:

Remote MCP endpoint:

x402 manifest:

Agent buyer guide:

Discovery:

Free readiness checker:

Free owner next step:

Directory reviewer / endpoint-owner fit check:

Downloadable listing packet:

## Fastest Buyer-Safe Path

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

1. Confirm the public manifests:
- MCP:
- x402:
2. Probe the cheapest paid endpoint without paying:
- `GET https://ontarioprotocol.com/api/x402/reputation/demo-agent`
- Expected: HTTP `402` payment challenge for `0.001 USDC` on Base.
3. Run the free policy check before any wallet action:
- `POST https://ontarioprotocol.com/api/agent/can-pay`
4. If you own an MCP/x402 endpoint, request a free public fit check:
-
5. Only make a paid call after your own policy allows USDC-on-Base settlement and you can store the payment quote/receipt.

Current boundary: Ontario has public crawler/developer-tool inspection and a self-funded `0.01 USDC` rail 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.

## Recommended Directory Description

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.

## Tools

| Tool | Method | Endpoint | Price |
| --- | --- | --- | --- |
| `agent_can_pay` | POST | `https://ontarioprotocol.com/api/agent/can-pay` | free |
| `x402_readiness_verify` | POST | `https://ontarioprotocol.com/api/verify/x402-readiness` | free |
| `agent_verify_payment` | POST | `https://ontarioprotocol.com/api/agent/verify-payment` | free |
| `discover` | GET | `https://ontarioprotocol.com/discover` | free |
| `agent-trust-scan` | POST | `https://ontarioprotocol.com/api/x402/agent-trust-scan` | 0.01 USDC |
| `reputation-lookup` | GET | `https://ontarioprotocol.com/api/x402/reputation/{agent_id}` | 0.001 USDC |
| `list-agent` | POST | `https://ontarioprotocol.com/api/x402/list-agent` | 0.10 USDC |
| `list-service` | POST | `https://ontarioprotocol.com/api/x402/list-service` | 0.50 USDC |

## If A Paid Probe Returns HTTP 402

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

```bash
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"}'
```

Expected boundary:

- `GET /api/x402/reputation/demo-agent` returns HTTP `402` with `Payment-Required` / `X-Payment-Required`, `quote_id`, `maxAmountRequired=1000`, `network=base`, and `payTo`.
- 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.

## Listing Purpose

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.

## Free-First Owner Path

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

- public fit-check form:
- owner handoff route: `GET https://ontarioprotocol.com/api/mcp-owner-next-step`
- human owner page:
- free mini-check request: `POST https://ontarioprotocol.com/api/mcp-mini-check`
- free listing validation: `POST https://ontarioprotocol.com/api/x402/list-service/validate`

The paid `list-service` route is only for owners who want a public Ontario catalog listing after the free checks are useful.

## Verification

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

```bash
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 accepts `POST /mcp` for JSON-RPC MCP calls. `GET /mcp` returns a `200` JSON discovery document with the manifest URL, POST usage, free owner next-step, and paid listing boundary.

For a full ingestion sequence, see [Directory Crawler Guide](DIRECTORY_CRAWLER_GUIDE.md).

For ranked owner-reviewed submission targets and evidence criteria, see [Directory Target Shortlist](DIRECTORY_TARGETS.md).

For observed external MCP crawler compatibility, see [Crawler Compatibility Receipt](CRAWLER_COMPATIBILITY.md).

For public accepted-listing evidence on agent-tools.cloud, see [agent-tools.cloud Listing Evidence](AGENT_TOOLS_LISTING_EVIDENCE.md).

## Evidence Contract

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.

## Boundary

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