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.
Agent Trust Scan
0.01 USDC
Submit an agent's card URL or A2A endpoint, receive a structured trust report (security signals, identity claims, declared capabilities). Returns JSON.
- Method
- POST
- Endpoint
https://ontarioprotocol.com/api/x402/agent-trust-scan
- Network
base
- Verified
-
READY
- Score
- 100/100
- Tags
- trust, scan, ai-agent, security
Agent Reputation Lookup
0.001 USDC
Look up an agent's accumulated reputation (sourced from on-chain EAS attestations on Base + recent scan history).
- Method
- GET
- Endpoint
https://ontarioprotocol.com/api/x402/reputation/<agent_id>
- Network
base
- Verified
-
READY
- Score
- 100/100
- Tags
- reputation, eas, attestation
Submit Agent Listing
0.10 USDC
Submit an AI agent for inclusion in the Ontario Protocol directory. Pays 0.10 USDC up front to deter spam.
- Method
- POST
- Endpoint
https://ontarioprotocol.com/api/x402/list-agent
- Network
base
- Verified
-
READY
- Score
- 100/100
- Tags
- directory, submit, agent
List a Third-Party x402 Service
0.50 USDC
Register your own x402-paid endpoint so AI agents discover it through Ontario Protocol's `/discover`. 0.50 USDC listing fee.
- Method
- POST
- Endpoint
https://ontarioprotocol.com/api/x402/list-service
- Network
base
- Verified
-
READY
- Score
- 100/100
- Tags
- marketplace, list, x402
Submit your own x402 service
POST your endpoint metadata to /api/x402/list-service
with a 0.50 USDC payment. Ontario verifies the submitted endpoint first.
Ready services appear here, in /discover,
and in Ontario’s machine-readable manifests (for example /.well-known/x402.json)
when their stored report grades ready.
See the docs for the full payload shape, plus the
list-service JSON Schema,
the service listing quickstart,
/discover listing checklist and the
pending → ready remediation playbook.
Free payload validation (no payment; does not store a listing): POST /api/x402/list-service/validate.
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 a listing payload (no payment)
Paste your JSON body here to check required fields and get a normalized payload before you run the paid
POST /api/x402/list-service.
What happens after you submit
- Ontario stores an initial readiness report and marks your listing
pending, needs_work, close, or ready.
/listings can show pending entries; /discover is filtered to strong evidence (default: ready).
- Fix issues using the report warnings, then re-run
/verify to store a fresh report.
- Status and pipeline health:
/api/listings/status.
# 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)
SDK examples: ontario_list_service.py ·
ontario-list-service.ts
Recommended first step: run the free verifier at /verify and fix warnings before submitting.