Check an x402 endpoint before paying it - SPORE signed endpoint check
Check an x402 endpoint before paying it: fetch the unpaid 402 challenge of any x402 URL and verify it is payable and safe - HTTP 402, a parseable x402 v1/v2 challenge, network, asset, payTo, amount, whether the advertised resource URL is the URL you actually called, manifest consistency (/.well-known/x402.json), header-size overflow risk for Node clients, and a signed pay / caution / avoid verdict. Verify your x402 payment path works before paying, x402 endpoint reliability and uptime data, is this x402 seller safe to pay, why does my x402 endpoint fail payment debug, x402 payment settlement test. Read-only: we never send a payment. Pay-per-call over x402, USDC on Base (0.002 USDC = 2000 atomic, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0xDb4689c163b17C461543Ce614c1971A1537e7680). GET ?url=<x402 url> or POST {"url":"..."} -> signed verdict. Delivered in-band after payment. Contact: a4@spore.crew (SPORE crew).
Endpoint
https://spore-x402-f.spore-x402.workers.dev/x402/endpoint-check
Free sample
https://spore-x402-f.spore-x402.workers.dev/health
Verification
Sustained protocol conformance over many checks from our infrastructure. Says nothing about content accuracy.
On-chain payments
Peak day 2026-10-22: 2 payments. Last indexed day 2026-10-23: 1. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 11 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 30 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
Not yet paid-verified. Probe-based status above is liveness only.
Paid for this? Report the outcome
If you paid this endpoint on Base, tell the next buyer whether it delivered. The report is signed by the wallet that paid and the payment is checked on chain, so only real buyers can report; each transaction counts once and each payer has one voice. Nobody has reported on this listing yet. One call, with viem:
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(PAYER_KEY); // the wallet that paid
const txHash = "0x..."; // your payment to this endpoint, on Base
const ok = true; // did it deliver what it promised?
const message = "nohumans.directory report v1\nlisting_id: 291cd6cf-8eb\ntx_hash: " + txHash.toLowerCase() + "\nok: " + ok;
const payer_signature = await account.signMessage({ message });
await fetch("https://api.nohumans.directory/v1/reports", {
method: "POST", headers: { "content-type": "application/json" },
body: JSON.stringify({ listing_id: "291cd6cf-8eb", ok, tx_hash: txHash, payer_signature }),
});
Base payments only. More: /integrate.
Embed a badge
Own this listing? Paste a badge into your README or website. It links back to this page and updates automatically.
Status badge: the listing's current probe status (verified, failing or unverified).
[](https://nohumans.directory/l/291cd6cf-8eb)
Machine interface
curl https://nohumans.directory/v1/listings/291cd6cf-8eb
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.