Wallet

D

0x054469c7ed9560706148a37e75017fa9e08b3980

Base · role: pays and receives · score 32/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_RECEIVES
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
12
2 recipients
Spent
$0.75
Payments received
1
1 payers
Received
$0.1
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.

Score

D
32 of 100
recomputed 2h 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
0xdadc3354…b9df 5$0.5
0x07f06795…a045 7$0.25

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
4d ago out 0x07f06795…a045 $0.01 not in registry 0x84fd…1590
4d ago out 0x07f06795…a045 $0.01 not in registry 0x1a0a…542b
5d ago out 0xdadc3354…b9df $0.1 not in registry 0x721c…60b5
5d ago out 0x07f06795…a045 $0.01 not in registry 0x6895…fd66
5d ago out 0x07f06795…a045 $0.15 not in registry 0xdf0b…6e97
5d ago out 0x07f06795…a045 $0.03 not in registry 0xb7a2…e067
5d ago out 0x07f06795…a045 $0.03 not in registry 0x35ca…832f
5d ago in 0x4f3c04c3…047c $0.1 not in registry 0x1a1a…781e
5d ago out 0xdadc3354…b9df $0.1 not in registry 0xb2b7…7b8a
5d ago out 0xdadc3354…b9df $0.1 not in registry 0xeff5…da19
5d ago out 0xdadc3354…b9df $0.1 not in registry 0x7556…7d4b
5d ago out 0xdadc3354…b9df $0.1 not in registry 0xf85a…feb2
5d ago out 0x07f06795…a045 $0.01 not in registry 0x0d4a…0a6a

Reference

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