Infoharmoni Atlas x402Base

Sellers / other / chainstate.schemasure.com

chainstate.schemasure.com

Profile a Base address in one call instead of four to six lookups. Returns contract or externally owned plus code size, proxy detection acro…

unclaimed pageBase1 endpointone of 9 hosts paid into one walletas of 21 October 2026

#673of 2,684 sellers, by paid calls
25paid calls in 30 days, as the registry reports
3payers in 30 days, as the registry reports (see notes)
$0.02price per call
$0.50est. money at list price · rank #715
-11%paid calls since 13 Oct 2026

Who actually paid

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

Payments to 9 hosts land in this same wallet — usually one operator, sometimes a platform collecting for several. The group’s page: schemasure.com.

Daily money · x402 USDC on Base · 14 Oct 2026 – 20 Oct 2026 · the wallet’s, across every host paid into it
14 Oct under $1 (6 payers) · 15 Oct $0 (0 payers) · 16 Oct $0 (0 payers) · 17 Oct $0 (0 payers) · 18 Oct under $1 (2 payers) · 19 Oct under $1 (1 payer) · 20 Oct under $1 (2 payers)

Relationships

16 buyers paid this wallet over x402 on 5 of the window’s 8 days: 18 payments, $0.36. 1 of 16 buyers came back on another day (6%).

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 1 endpoint in the registry, by paid calls over 30 days; price and chain per endpoint.

endpointpaid callspayerspricechain
/v1/chain/state253$0.02Base

The replay

2026-10-13: 28 paid calls (30 d)2026-10-14: 28 paid calls (30 d)2026-10-15: 28 paid calls (30 d)2026-10-16: 28 paid calls (30 d)2026-10-17: 28 paid calls (30 d)2026-10-18: 28 paid calls (30 d)2026-10-19: 28 paid calls (30 d)2026-10-20: 26 paid calls (30 d)2026-10-21: 25 paid calls (30 d)
2026-10-132026-10-21

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
node-starter--maxujon18.replit.app3$0.01x402 v2 paid EVM token contract risk API on Base and BSC. For 0.01 USDC, returns EIP-1967 proxy detection, own
nbx4.dev2$0.02Analyze a Base Mainnet token contract: block-pinned owner(), ERC-1967 proxy slots, ERC-20 metadata, code hash,
ippulse.waltsoft.net6$0.005IP reputation, geolocation, ASN lookup — proxy/VPN/Tor detection, abuse scoring, and open port analysis for an
token-facts.x402supply.com1$0.005Onchain facts for a Base ERC20 address: ERC20 shape, honeypot-style selectors and an ungraded adminPowers prof
automaton-tx-explainer.vercel.app38$0.005–$0.25Inspect any Base address: EOA vs contract vs EIP-7702 delegated, ETH balance, nonce, proxy implementation (EIP
app.metalift.ai68$0.005Metalift scrape: URL → LLM-ready markdown with WAF/retail escalation, JS render, and residential proxy when ne
x402-data-api.sigrunner.workers.dev125$0.001–$0.01Token security / honeypot detector for a Base mainnet ERC-20: EIP-1967/1822 proxy + upgradeability detection,

Going rate, the median of the 7 matched sellers with a listed price (of 7 matched): $0.005 a call. This seller charges $0.02, which is over it.

How to read these numbers