Ontario Protocol.
For MCP and x402 service owners

Make your paid MCP endpoint safe enough for agents to call

Agent buyers need more than a checkout link. They need to know the endpoint exposes a real HTTP 402 challenge, a matching x402 manifest, Base USDC payment metadata, a readable MCP surface, and evidence that a payment can settle before an autonomous wallet spends.

What Ontario can prove

Ontario gives MCP owners a public readiness path: free verification first, then an optional 0.01 USDC paid trust scan that proves the payment rail end to end. The result is point-in-time evidence, not a guarantee of future safety, legal compliance, or payment outcome.

The buyer checklist agents look for

HTTP 402 challenge

The endpoint must declare price, network, asset, resource, and retry instructions.

x402 manifest

The public manifest should match the actual paid resource and Base USDC metadata.

MCP discovery

Agents need a clear MCP entry point, tool description, and safety boundary.

Settlement proof

A paid call should produce verifiable transaction and report evidence.

Run the free readiness check

Start with a no-money readiness scan. It checks whether an agent can understand your endpoint before any wallet signs a payment. 

curl -sS 'https://ontarioprotocol.com/api/agent/can-pay?url=https://YOUR-DOMAIN.example/.well-known/x402.json' | jq .

Then prove the paid rail

If the free checks pass, run one small paid call against Ontario's live endpoint and compare the response with the public treasury ledger. This is the fastest evidence path for an MCP owner who wants agents, directories, or marketplaces to trust a paid tool.

Free mini-check, then a paid packet if it is worth fixing

If you run a paid MCP or x402 endpoint and want agents to call it, start with a free endpoint mini-check. Ontario reviews the public challenge, manifest, MCP discovery, and buyer-facing payment metadata. If the endpoint is close enough to be worth fixing, the paid packet turns that into a buyer-safe verification summary and shippable fix list.

Free mini-check

One public endpoint, quick pass/fail notes, and the first blocker an agent buyer would hit.

$199 verification packet

One endpoint, one buyer-safe summary, deeper readiness notes, and a fix list. No guarantee of future revenue or safety.

Success signal

Your endpoint becomes easier for agents, directories, and marketplaces to evaluate before spending.

Request free mini-check View pricing boundary

Request the free mini-check

Two fields only. If the endpoint is public, Ontario can inspect the rest.

Optional context

Prefer manual contact? Email hello@ontarioprotocol.com with your endpoint URL and the agents you want to support.

Current live proof boundary

Ontario has a self-funded settled rail proof. That proves the payment path can work, but it is not customer revenue and should not be described as buyer validation.