Wallet

F

0xdf1b6e9ae298a1c65193831a05c56cea4c3343a9

Base · role: pays and receives · score 24/100

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_RECEIVESSINGLE_COUNTERPARTY
0%
agent likelihood

Measured from how evenly the payments are spaced: a machine keeps the same interval, a human does not. Here the intervals are irregular, which does not look automated.

Regular intervals mean automation, not necessarily an AI agent: a cron script looks exactly the same. TRM Labs put the share of value from autonomous agents at somewhere between 0.6% and 7.5%; the rest is ordinary scripts.

That is why agent likelihood is reported separately rather than folded into the score.

Payments sent
16
1 recipients
Spent
$2.31
Payments received
1
1 payers
Received
$0.5
First seen
4d 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.

Score

F
24 of 100
recomputed 13h ago

We look at the age of the address, how long and with whom it has been transacting, how varied its counterparties are, and whether it appears on sanctions lists. A sanctions hit zeroes the score outright — that is about permissibility, not quality.

The exact methodology is not published yet.

Pays to

RecipientPaymentsAmount
0x5c4e97de…a0fd 16$2.31

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
3d ago in 0x1cc884f0…c2f0 $0.5 not in registry 0x353c…4933
4d ago out 0x5c4e97de…a0fd $0.11 not in registry 0xf353…e1a8
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0x7e2c…4941
4d ago out 0x5c4e97de…a0fd $0.13 not in registry 0x8175…a971
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0x6775…4359
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0xafa1…b558
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0x61e9…c17c
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0x0a25…3452
4d ago out 0x5c4e97de…a0fd $0.11 not in registry 0xccc1…dcf0
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0xb048…d9bc
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0xc16b…989d
4d ago out 0x5c4e97de…a0fd $0.1 not in registry 0x6e75…7f98
4d ago out 0x5c4e97de…a0fd $0.28 not in registry 0x81c7…e843
4d ago out 0x5c4e97de…a0fd $0.42 not in registry 0x5050…593a
4d ago out 0x5c4e97de…a0fd $0.11 not in registry 0xb016…0e7f
4d ago out 0x5c4e97de…a0fd $0.13 not in registry 0xfc9b…8203
4d ago out 0x5c4e97de…a0fd $0.22 not in registry 0xfac9…7152

Reference

Address0xdf1b6e9ae298a1c65193831a05c56cea4c3343a9
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.