StallRow — Receipt Verify
Receipt Verifier — a Base transaction hash in, a normalized verified receipt out: payer, payTo and amount from the USDC Transfer log, asset and network, settled status and confirmations. When the payTo is this fleet's own and the amount matches a priced route, routes at that price are listed as candidates — an amount alone never proves which route was called. Unknown transactions error honestly, unsettled. Use this when someone claims they paid and you want the chain's version. Base only.
Endpoint
https://stall-row-production.up.railway.app/v1/receipt-verify
Free sample
https://stall-row-production.up.railway.app/sample/receipt-verify
Verification
We paid this endpoint real USDC and confirmed settlement on-chain; the response was inspected.
On-chain payments
Peak day 2026-10-25: 78 payments. Last indexed day 2026-11-06: 11. 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 40 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
✓ verified with real payment — 2026-11-01
$0.002 USDC paid on Base · tx ↗
response: valid JSON, matched declared schema
Real USDC was paid to this endpoint and the response inspected — not just a liveness check. Purchased at the date shown; delivered listings are bought again over time, and a later purchase that did not deliver is shown here.
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: 8f41ab60-b9d\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: "8f41ab60-b9d", 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/8f41ab60-b9d)
Paid badge: we paid this endpoint with real USDC and it delivered. ×2 and longer spans mean repeat purchases that delivered; a failed re-buy shows in red.
[](https://nohumans.directory/l/8f41ab60-b9d)
Machine interface
curl https://nohumans.directory/v1/listings/8f41ab60-b9d
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.