Infoharmoni Atlas x402Base

Sellers / other / kertivo.com

kertivo.com

Full-history address-poisoning check before you send USDC on Base. Same risk/lookalike/seenBefore logic as /address/check, but funding histo…

unclaimed pageBase3 endpointsone of 3 hosts paid into one walletas of 8 November 2026

#1076of 3,250 sellers, by paid calls
16paid calls in 30 days, as the registry reports
10payers in 30 days, as the registry reports (see notes)
$0.005–$0.05price per call, across 3 endpoints
$0.14est. money at list price · rank #1427
+129%paid calls since 31 Oct 2026

Who actually paid

In the last 24 h on Base, no x402 payment reached this seller’s wallet.

Payments to 3 hosts land in this same wallet — usually one operator, sometimes a platform collecting for several. The group’s page: hectichustle.workers.dev.

Daily money · x402 USDC on Base · 1 Nov 2026 – 7 Nov 2026 · the wallet’s, across every host paid into it
1 Nov no data · 2 Nov under $1 (4 payers) · 3 Nov no data · 4 Nov $0 (0 payers) · 5 Nov under $1 (2 payers) · 6 Nov $0 (0 payers) · 7 Nov $0 (0 payers)

Relationships

6 buyers paid this wallet over x402 on 3 of the window’s 8 days: 10 payments, $0.04. 1 of 6 buyers came back on another day (17%).

In the full record: its most loyal buyers, what is bought alongside it, who left it for whom, who came to it from where, and its early buyers, each with the counts behind it. How to get it: the $0.001 check over x402, Atlas Pro at $49 a month and for the seller itself, the Your buyers report at $29 a month.

Relationships are patterns in the x402 payments we observe on Base over the window: a buyer is a wallet that paid this seller’s payTo wallet, and came back means it paid on two or more different days. A wallet is not an agent, and a relationship is a pattern of payments, not a claim about who anyone is or who runs a wallet.

Is this your service? See who your buyers are: every wallet that paid you, day by day, and where the ones that left went, in one report.

Endpoints

The busiest of this seller’s 3 endpoints in the registry, by paid calls over 30 days; price and chain per endpoint.

endpointpaid callspayerspricechain
/address/check/full127$0.005Base
/check32$0.01Base
/check/deep11$0.05Base

The replay

2026-10-31: 7 paid calls (30 d)2026-11-01: 7 paid calls (30 d)2026-11-02: 11 paid calls (30 d)2026-11-03: 12 paid calls (30 d)2026-11-04: 14 paid calls (30 d)2026-11-05: 16 paid calls (30 d)2026-11-06: 16 paid calls (30 d)2026-11-07: 16 paid calls (30 d)2026-11-08: 16 paid calls (30 d)
2026-10-312026-11-08

Selling something like this

Matched automatically from each seller’s own short description. It will sometimes be wrong; tell us and we fix it.

sellerpaid callspricesells
paycheck.hectichustle.workers.dev76$0.001–$0.05Address-poisoning check before you send USDC on Base. Body {from, to} (or sender/recipient; chain=base, token=
audit.liquidlogicx.com14$0.001–$0.03Check an agent wallet's x402 spend cap before it pays, via Liquid Logic X: send a wallet and optional endpoint
fetchgate.dev2$0.001–$0.01Base token risk check before a swap: send a token contract address, get ok / caution / avoid with reasons. Rea
address-poisoning-check.nextill-pos.workers.dev12$0.005Address-poisoning check before an agent or wallet sends crypto: pass the sending wallet and recipient; we scan
scaudit.madebydevx.com1$0.9Quick Solidity pre-audit check, $0.90 USDC on Base: send source or a … contract address + chain; the sa
svc.cipherowl.ai6$0.09–$2CipherOwl ExpressScan Basic: direct-address risk check. One address per request. Seven-day same-address rechec
trust-check.gm-tools.workers.dev5$0.002–$0.003Is this address safe to send funds to on Base? Checks scam blacklists, address poisoning (look-alikes of your
hoodrugcheck.com4$0.02Rug-risk check for a Robinhood Chain (chain 4663) token. Send {"address": "0x…"} and get a 0-100 safety score,

Going rate, the median of the 30 matched sellers with a listed price (of 30 matched): $0.01 a call. This seller’s endpoints run $0.005–$0.05, and the going rate falls inside that range — so no single over/under verdict is fair. Compare per endpoint.

How to read these numbers