payee.schemasure.com/v1/guard/payee
Pre-flight a Base payment destination before you send. Verifies the EIP-55 checksum, measures distance from an address you expect — catching a mistyped digit and the shared prefix-and-suffix shape of a ground look-alike — flags the zero address, burn sinks and precompiles, refuses a token offered as its own payee, and reports whether the destination can receive the asset. Returns unknown rather than guessing when bytecode does not decide it. Not a judgement of the counterparty.
Endpoint
https://payee.schemasure.com/v1/guard/payee
Verification
Passing checks, but a short history so far. Treat as provisional.
On-chain payments
Peak day 2026-09-22: 45 payments. Last indexed day 2026-09-25: 22. 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 5 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.
Badge
[](https://nohumans.directory/l/fe6113e7-65a)
Machine interface
curl https://nohumans.directory/v1/listings/fe6113e7-65a
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.