Live x402 Endpoint Readiness Benchmark
This benchmark is generated from Ontario's verification graph. It should become more valuable as external services submit endpoints and recurring monitors add history.
Current Benchmark
1117 reports
Signed readiness reports in the local verification graph.
4 ready services
3 currently meet Ontario Certified x402 in the local graph.
| Service | Score | Certification | Reports |
|---|---|---|---|
List a Third-Party x402 Servicehttps://ontarioprotocol.com/api/x402/list-service |
100/100 | Ontario Certified x402 | 25 |
Submit Agent Listinghttps://ontarioprotocol.com/api/x402/list-agent |
100/100 | Ontario Certified x402 | 25 |
Agent Trust Scanhttps://ontarioprotocol.com/api/x402/agent-trust-scan |
100/100 | Ontario Certified x402 | 25 |
https://the402.tateprograms.com/api/x402/skill-trust-checkhttps://the402.tateprograms.com/api/x402/skill-trust-check |
90/100 | Ready | 3 |
https://agoragentic.com/api/x402/invoke/01b48dd7-3ff9-4008-86bf-b5b7102a8d6bhttps://agoragentic.com/api/x402/invoke/01b48dd7-3ff9-4008-86bf-b5b7102a8d6b |
72/100 | Not certified | 1 |
How to read the benchmark
A single ready report is useful. A history of ready reports with valid signatures and stable metadata is stronger.
Evidence: Service profiles expose history_count, ready_count, average score, latest report, and certification level.
Fix: For production agents, prefer Ontario Certified x402 over a one-off ready result.
Sources
- Google AI Search optimization guide
- Coinbase x402 client/server flow
- Base x402 guide
- x402 docs: HTTP 402 core concepts
- x402 reference implementation (GitHub)
- Research: Five Attacks on x402 Agentic Payment Protocol (arXiv:2605.11781)
- Research: Hardening x402 with PII-safe metadata filtering (arXiv:2604.11430)
- Model Context Protocol tools specification