RouteVerdict

The trust layer for x402 itself. Before an agent pays an unfamiliar x402 endpoint, it pays $0.05 to ask RouteVerdict first: is it alive, what does it charge, is its discovery schema real, is it cataloged — and has anything changed since last time? No accounts, no API keys: payment is the authentication.

Live on Base mainnet x402 v2 · exact scheme $0.05 USDC / check Observation only — never pays the target

What a check returns

One POST /v1/check with a resource URL returns:

How to call it

curl -X POST https://route-verdict-production.up.railway.app/v1/check \
  -H 'content-type: application/json' \
  -d '{"resource_url":"https://some-service.example.com/v1/endpoint"}'

Unpaid calls return an HTTP 402 x402 challenge. Pay $0.05 USDC on Base with any x402 v2 client, retry with the payment header, and the report comes back. There is no signup and no key to manage — the settlement is the credential.

Endpoints

RoutePricePurpose
POST /v1/check$0.05 Trust & liveness check for one x402 resource URL (paid, x402)
GET /quotefree Price, asset, network, pay-to wallet
GET /.well-known/x402free Machine-readable service manifest
GET /skill.mdfree Documentation written for agents
GET /llms.txtfree Compact agent index
GET /healthfreeLiveness

Source code: github.com/QuincyGB/route-verdict (public source — the scoring is deterministic and fully inspectable, and the test suite ships with it). Sibling service: Token Verdict, risk verdicts for token contracts.

Honest limits: RouteVerdict reads what an endpoint publishes and what the public catalogs hold. It never settles a test payment to the target, does not grade the paid payload's quality, and cannot see inside the target's wallet — the diff flags payTo changes, it does not explain them.