x402 seller trust leaderboard

An autonomous agent about to pay an endpoint it has never used has almost nothing to go on. So we sweep the public x402 catalogue — one representative endpoint per origin — and score each origin from the outside using the same trust layer we sell: unpaid 402 behaviour, challenge conformance, discovery documents, on-chain payTo reputation and price sanity.

294origins scored
83.0median score
81.9mean
0unreachable
2026-11-18 20:42checked (UTC)
A score is a point-in-time judgement from the outside — not an audit, not an endorsement, and not a statement about whether a seller delivers. One endpoint per origin is probed; an origin may run others. Each row was checked at the time above; scores move as sellers change.

Our own numbers (call provenance)

52settled calls since 2026-10-07
24from outside callers
0USDC transfers in, last 24h, from outside
2026-11-19 04:42counted (CST)
We do not generate traffic to our own endpoints to climb the x402scan board. The board ranks by settled transaction count; rank 10 needs roughly 1,130 settled calls a day and we do not manufacture them. Every number above is a count and is reproducible: the gate log is our own request table filtered by method+path, the transfers are read from Base. Amounts are deliberately never published.
Three units, named, because a registry count, a gate log and a scanner count different things: 60 paid attempts, 52 settled (paid row, status 200, route matching the request method) and 408668 rejected challenges handed back with 402, since 2026-10-07. x402scan and the Bazaar crawler read settled transfers on-chain, so their number will not equal any of these three; when we quote theirs we say whose it is.
Counting rules, and the board thresholds we measured (2026-10-07): place 10 on x402scan's 24-hour server board needs about 1130 settled calls a day, its 100th place about 40, and a place on the board at all about 22. We publish where we are instead of buying a position. This section is rebuilt from adengine/data/provenance.json: the call count is our own request table filtered by method+path, the transfers are counted from Base logs, and transfers from our own test wallets are excluded (they exist to exercise the product, so a test payment is not counted as a buyer). We publish counts and never amounts - not the balance, not what a call earned us - and we say whose measurement a number is whenever we quote somebody else's.

Independent checks on us

The section above scores other people's endpoints. The same question applies to us, and the answer should not come only from us, so here is a third party that probes us independently and documents its band table.

healthytheir live probe verdict
71 · Trustedtheir tracked score, band 70-84 (2026-10-10)
100%their 30-day healthy-probe share for our resource
PulseFeed (pulsefeed.dev) crawls the public x402 catalogue, probes endpoints and publishes a 0-100 trust score with published bands: verified 85-100, trusted 70-84, caution 35-69, avoid 0-34, unknown = not indexed. Their live check on https://xhagents.xyz/api/x402-trust reported valid: true, verdict healthy and a tracked score of 71 (Trusted) on 2026-10-10, paid for by us with our own buyer wallet. Read it yourself, unfiltered: their free verify for xhagents.xyz — today it answers unknown / not indexed yet, because the origin itself is not in their index, so the number above comes from the paid live check on a resource, not from the origin. If any figure here has moved since the date shown, this section is out of date until we recompute it - which is why the date is in it.

A claim we corrected in the open

We publish machine-readable status documents, and when one of them stops being true we change the document and say so here instead of quietly leaving the old number up. The first time we had to do it is the example: our Bitcoin mining status file. It was first published with a field that read as a working hashrate figure. We then decided not to mine on this host, so the file now states that the worker runs in watch mode with no hashing at all, and the only hashrate number left in it is labelled as a measured capability rather than a production rate. No product, endpoint or price was added together with the correction.

field in the filevalue we publish
worker.operation_modewatch (pantau pool + pembayaran masuk, 0% CPU)
worker.active_hashingfalse
worker.measured_cpu_capability_hs1,143,976 H/s (about 1.14 MH/s) - a capability measured by a benchmark, not a production rate
worker.capability_sourcebenchmark lokal saat ini
as_of_utc2026-11-08T16:40:42Z
sha256 of the exact bytes served above280b06ecd6039a1d0a2fedc00bb51f7185c85babbe30b5494a9305f6de2d0cd5
Read it yourself, unfiltered: /.well-known/btc-mining.json — every value in the table above is rendered from that file when this page is built, and the last row is the SHA-256 of the exact bytes served, so the two can be compared byte for byte without trusting this page. The file also states what it does not claim: not a hashrate service, not custody, and it never asks for a private key. This page quotes the fields above and nothing else from the file.

Most trusted (top 25)

#originscoreverdictendpointspayTomain finding
1https://search.gedx402.com97pay500xb3C2776cE3…payTo is an EOA running a smart-wallet delegation (0x63c0c19a…) — the key holder still controls the funds
2https://api.polls.karbach.digital97pay460x6d8444CaEd…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
3https://agentx.sale97pay330x9702dDF83E…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
4https://api.interzoid.com97pay520xdCEca23FF8…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
5https://x402.pulsescanner.io97pay460x4842a7d5b2…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
6https://eltociear-tokenguard.hf.space97pay450x5bCDA55247…payTo is a plain EOA (no contract can freeze the funds)
7https://mcp.x-ray.me97pay360x9e008b8C7D…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
8https://x402.pokt-agent.com97pay320xC724e18704…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
9https://toolrail.dev97pay300xC6E6138dAA…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
10https://data.greeneris.io97pay300x6ab8efe305…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
11https://bot-bazaar.fly.dev93pay1980x847f54ae8d…openapi.json documents this path without an input schema
12https://x402-niche-briefs.fly.dev93pay1450x847f54ae8d…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
13https://1gateway.dev93pay1420x6246eee035…openapi.json is not valid JSON
14https://agentshield.live93pay1290xC87e9a5F23…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
15https://shop.lordevo.com93pay590x0876A79Bb5…openapi.json is not valid JSON
16https://agents.crowdspark.me93pay560x0dEA0030A1…openapi.json documents this path without an input schema
17https://sift.srv1996466.hstgr.cloud93pay580x33d25C0A91…openapi.json documents this path without an input schema
18https://tariffmonkee.com93pay390x0FAD15c9f4…openapi.json documents this path without an input schema
19https://agent402.tools93pay6270xaBF4FAbd7c…openapi.json is not valid JSON
20https://api.x402node.dev93pay3270x4466d4A84b…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb
21https://x402.freeq.one93pay1640x90b0dC8934…openapi.json documents this path without an input schema
22https://api.aiskills402.com93pay1780xbc0dcc70d8…openapi.json is not valid JSON
23https://agent.pocket.network93pay1200xF732ea490c…openapi.json is not valid JSON
24https://api.blockchainmoneymap.com93pay1090x2211E12e6B…openapi.json is not valid JSON
25https://stack.halowerk.com93pay1060x2880EdfFF1…openapi.json is not valid JSON

Lowest scoring

#originscoreverdictendpointspayTomain finding
1https://saylorinnovations.com22avoid132…probed twice, 503 then 503: the route served no payment terms either time
2https://cities-factory-live.wuryan529.workers.dev22avoid750…probed twice, 429 then 429: the route served no payment terms either time
3https://ask.singitai.app24avoid73…probed twice, 200 then 200: the route served no payment terms either time
4https://minha-api-x402.igor-3d2.workers.dev25avoid30…probed twice, 400 then 400: the route served no payment terms either time
5https://api.getanyapi.com25avoid33…probed twice, 400 then 400: the route served no payment terms either time
6https://mcp.xrpl-utilities.io26avoid56…probed twice, 406 then 406: the route served no payment terms either time
7https://kristo-intelligence-api.onrender.com29avoid26…probed twice, 400 then 400: the route served no payment terms either time
8https://agent-toolbox.zafermemon87.workers.dev29avoid36…probed twice, 406 then 406: the route served no payment terms either time
9https://tanod.dev29avoid596…probed twice, 400 then 400: the route served no payment terms either time
10https://agentapimarket.com29avoid24…probed twice, 400 then 400: the route served no payment terms either time
11https://api.craigmbrown.com29avoid38…probed twice, 405 then 405: the route served no payment terms either time
12https://forge-tools.dentreprise.workers.dev33avoid42…probed twice, 400 then 400: the route served no payment terms either time
13https://aipaygen.com33avoid222…probed twice, 400 then 400: the route served no payment terms either time
14https://sovereign-x402-zeta.vercel.app37avoid30…no reachable .well-known/x402 discovery document
15https://pulse.xrpl-utilities.io43avoid29r9sr13PJ4u6Z…the POST probe answered without a challenge while GET returned the 402: an agent has to pick the right verb

Verdict spread

verdictorigins
avoid15
pay204
pay_with_caution75

Why scores were lost

penaltyoccurrences
openapi.json is not valid JSON150
payTo reputation NOT measured146
payTo is a plain EOA (no contract can freeze the funds)96
the POST probe answered without a challenge while GET returned the 40291
the resource is not listed in its own .well-known/x402 document83
.well-known/x402 is not valid JSON76
no reachable .well-known/x402 discovery document48
openapi.json documents this path without an input schema42
payTo is an EOA running a smart-wallet delegation (0x63c0c19a…) — the 23
no reachable openapi.json23
25 USDC inflows from 6 sender(s) on record21
6 distinct senders = more than one buyer's word for it21

Reproduce any row

One endpoint, live, in one paid call — POST https://xhagents.xyz/api/x402-trust with {"url": "…"} gives you the same 0-100 report with the evidence and the penalties. The price is deliberately not written here: the live 402 challenge quotes it, and openapi.json records it per operation, so a price change needs no edit on this page.

The full ranking as JSON, filterable by verdict and score, is one paid call — GET https://xhagents.xyz/api/trust-leaderboard?limit=100&order=worst. Free method page and top-ten preview: /api/trust-leaderboard/method.

Every endpoint is listed with its price in openapi.json and /.well-known/x402.

Who we are, verifiably

Everything above about our own endpoints is checkable without trusting us: /.well-known/seller-attestation.json binds this domain and the one USDC receiving address to a single ed25519 key, and carries the SHA-256 of this catalogue (ard.json), the pre-purchase evidence pack (x402-evidence.json) and openapi.json. Re-hash those three files from this domain and verify the signature offline — no call back to us is needed.

Before paying us, read x402-evidence.json: for every paid route it states the price and destination measured from the live 402 challenge, the input schema and an output example we publish, the free method page where the same engine answers without payment, and how often the route actually converted (counted in our own request log, with the definitions printed next to the numbers).

Method

one representative endpoint per origin, scored with XH Agents' x402 trust layer: unpaid 402 probe, challenge conformance, discovery documents, on-chain payTo reputation (USDC inflows seen by a transfer indexer; Solana via public RPC), price sanity

Not checked: behaviour after payment (whether a seller delivers), uptime over time — each row is a point-in-time probe, operator identity, content accuracy, payTo reputation is a bounded look at the last 25 incoming USDC transfers; a row that says 'NOT measured' means the indexer or RPC refused the query, not that the address is empty, origins that sell on other chains than Base and Solana: their payTo cannot be inspected this way.

Unreachable at sweep time: 0 origins