Wallet

?

0xe8dc41f9e675ba8340140c99180cfaee65d4d160

Base · role: pays and receives · not enough data

Buyer-side scoring — something no other public x402 service offers. It answers the seller's question: should I serve this agent, and how large a channel should I open for it?

PAYS_AND_RECEIVES
Payments sent
1
1 recipients
Spent
$0.02
Payments received
3
1 payers
Received
$4.92
First seen
5d ago
This address both pays and receives. On its own that proves nothing — an operator may pay for other APIs and sell its own. But combined with heavy concentration on a single counterparty it starts to look like volume inflation, and we flag it.
A score needs more than a single payment to mean anything.

Pays to

RecipientPaymentsAmount
0xae393a9c…b42c 1$0.02

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
4d ago out 0xae393a9c…b42c $0.02 not in registry 0xff22…3c1b
4d ago in 0x0d24cd72…a4ff $1.64 not in registry 0x163e…c011
5d ago in 0x0d24cd72…a4ff $1.64 not in registry 0xa439…26ec
5d ago in 0x0d24cd72…a4ff $1.64 not in registry 0xa193…e889

Reference

Address0xe8dc41f9e675ba8340140c99180cfaee65d4d160
NetworkBase eip155:8453
Sanctions screeningclear
Machine access/v1/wallet · /full · external explorer

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Endpoints →

Scores, findings and the full observation history per resource.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.

We hold no fundsNo custody, no escrow, no facilitator role. Not one payment passes through us.
Same input, same answerScoring is deterministic. No model, no learning on the fly.
Objections welcomeWe show owners what drags a score down. How to dispute
We say what we can't seeSome payments move off-chain, and we say so instead of pretending otherwise.