You expose an endpoint agents could pay for, but the payment story is unclear or unproven.
Turn crawler attention into a buyer-safe paid endpoint path.
If agents, directories, or developer tools can find your MCP or x402 endpoint but nobody buys, the problem may be trust evidence: price metadata, payment challenge, manifest quality, MCP discovery, and proof that a wallet can safely decide before spending.
Who this is for
You want agent hubs and directories to understand what your tool sells and how payment works.
You need public evidence before a listing, submission, or buyer handoff makes sense.
You have crawler hits, clicks, or stars, but no qualified buyer request or paid call yet.
Audit scope
- HTTP 402 challenge fields: price, resource, network, asset, and retry instructions.
/.well-known/x402.jsonand/.well-known/mcp.jsonconsistency.- Agent-facing copy: what the buyer gets, what it costs, and what evidence exists.
- Directory and marketplace readiness for MCP, x402, and developer tool catalogs.
- One buyer-safe action plan that separates free checks from paid calls.
Run the local proof path first
Ontario keeps the first step free and evidence-based. Check whether a machine can understand the endpoint before asking any wallet to sign.
curl -sS 'https://ontarioprotocol.com/api/agent/can-pay?url=https://YOUR-DOMAIN.example/.well-known/x402.json' | jq .
Revenue truth boundary
This page is an owned public distribution surface. It can create crawler and click evidence, but it is not customer revenue. Ontario should count revenue only after a real mini-check request, buyer reply, signup, paid call, or payment is recorded. The audit is not a guarantee of future revenue, safety, legal compliance, listing acceptance, or marketplace approval.
Reference proof
Ontario's own live rail proof is the benchmark example. It proves the rail can settle; it does not prove external buyer demand.
- Transaction:
0xfef2cde26dcdc30dfa9d5e799228c5a8f59d3c392100e6a13c9ac2dcf4d59c5a - Signed report:
vrf_0996ca3c6ea6f361 - Ledger:
https://ontarioprotocol.com/api/treasury/ledger?limit=10