api.m2msentinel.com/v1/audit/:address
Before you sign: can this Base contract be paused, frozen, or have tokens minted by its owner, self-destruct, or delegate execution somewhere you have not seen? Returns the opcodes and selectors actually present in the deployed bytecode, resolves proxies and EIP-7702 delegated accounts to what really runs, and states the trust level behind the answer. Evidence for your policy, not a safety verdict.
Endpoint
https://api.m2msentinel.com/v1/audit/:address
Verification
On-chain payments
Payment shape (25 most recent sampled): 25 x402-signed (EIP-3009 transferWithAuthorization, the exact scheme's on-chain signature) · 0 plain transfers (a wallet paying the ordinary way) · 0 other calldata (facilitator batch, smart wallet, or unrelated — not classified).
Peak day 2026-08-24: 7 payments. Last indexed day 2026-09-03: 3. Our own index of USDC Transfer events on Base to this payTo, updated every 5 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 9 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 7 probes, oldest → newest · 100% pass · re-probed several times an hour from nohumans infrastructure — never self-reported
Paid verification
Not yet paid-verified. Probe-based status above is liveness only.
Badge
[](https://nohumans.directory/l/e9bc83c6-388)
Machine interface
curl https://nohumans.directory/v1/listings/e9bc83c6-388
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.