Discovery should be evidence-backed. Listings carry verification status
from Ontario's x402 readiness checker; third-party endpoints enter
/discover only when they are verified or score ready.
Ontario Protocol provides readiness and trust signals based on observable endpoint behavior,
manifest metadata, payment challenge behavior, report history, and public evidence.
It does not guarantee endpoint safety, service quality, financial outcome, or future behavior.
Agents should still enforce budget, policy review, and independent verification before spending.
For providers: prepare the listing before paying
Run the free agent catalog readiness scorecard first.
It checks public x402 endpoint behavior, GitHub launch evidence, and MCP Registry metadata when supplied,
then returns a report ID and the highest-impact next action. A listing fee buys directory submission,
not guaranteed traffic, ranking, safety, or agent purchases.
Ontario listing, MCP Registry, and Coinbase Bazaar are separate distribution surfaces.
A listing or metadata file does not itself create a Bazaar placement. For Bazaar-enabled
routes, Coinbase documents cataloguing after the CDP Facilitator observes a successful
settlement. That activation event belongs to the provider; Ontario cannot force or
guarantee catalog placement, traffic, ranking, or purchases.
Run the free catalog scorecard and fix the report's endpoint, price, network, manifest, and registry mismatches.
Rehearse the same challenge and retry flow on your sandbox or Base Sepolia setup before touching production funds.
Only after the endpoint owner approves the policy, make the smallest controlled production settlement through an approved x402 client and retain the report ID, payment response, and transaction evidence.
Re-check Ontario and the external catalog. Treat placement as unconfirmed until the catalog actually returns the resource.
Provider boundary: Ontario never asks for private keys, seed phrases, or wallet custody,
and it does not execute a production purchase on your behalf. Read the
official Bazaar discovery documentation
before approving any settlement.
8 total services8 first-party0 third-party0 verified0 pending0 auto-verifiedJSON catalog →
AllTrustDirectoryMarketplaceDataAgentOther
Ontario x402 Paid API Preflight0.002 USDC
Verify an x402 endpoint before an AI agent pays. This x402 paid API verification service and AI-agent tool runs a fresh payment preflight for an autonomous agent: inspect the live HTTP 402 challenge, payTo address, price, Base USDC network and asset, manifest readiness, buyer budget, and spend policy. Returns ALLOW or DENY with reasons, a report ID, settlement metadata, and a settlement-backed SHA-256 evidence receipt. Run free can-pay and readiness checks first. Readiness evidence is not a safety guarantee.
Pay-per-review implementation evidence for a public x402 endpoint or GitHub repository. Returns actionable payment, discovery, security, debugging, and launch findings without returning source contents or secret values. Run free checks first.
Classify up to 20 Base USDC settlement receipts as direct self-payment, user-declared related-party, or unattributed. Unattributed wallets are not counted as proven customers.
Sandbox rehearsal (no spend; does not store a listing): POST /sandbox/api/x402/list-service.
This endpoint still returns HTTP 402 first so you can test your x402 client integration end-to-end.
Validate or submit a pending listing (no payment)
Paste your JSON body here to validate it or store a free pending entry. Pending entries are not recommendations
and are excluded from strict /discover results until evidence is ready. Set verify_now: true
to receive a free report summary with the response.
# 1) Probe the listing endpoint (expect HTTP 402, no payment signature yet)
curl -i -X POST https://ontarioprotocol.com/api/x402/list-service \\
-H "Content-Type: application/json" \\
-d '{"name":"Example Service","description":"Paid endpoint","endpoint":"https://example.com/api/paid","method":"POST","price_usdc":"0.01","network":"base","owner_url":"https://example.com"}'
# 2) Then pay + retry using an x402 client (see /docs#list-service)
# Sandbox: rehearsal endpoint (still challenges with HTTP 402, but settlement is simulated and no listing is stored)
curl -i -X POST https://ontarioprotocol.com/sandbox/api/x402/list-service \\
-H "Content-Type: application/json" \\
-d '{"name":"Example Service","description":"Paid endpoint","endpoint":"https://example.com/api/paid","method":"POST","price_usdc":"0.01","network":"base","owner_url":"https://example.com"}'
# Then pay + retry using your x402 client against /sandbox/api/x402/list-service (see /docs#list-service)