Wallet

F

0xf16f0882de08315b438e9f3a2abfb2d2e5d94eca

Base · role: pays and receives · score 28/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
6
3 recipients
Spent
$0.18
Payments received
11
2 payers
Received
$0.07
First seen
6d 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
28 of 100
recomputed 1d 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
0xb075aa82…59d8 4$0.16
0x79ebde4b…7d53 1$0.01
0xab62452b…a7bf 1$0.01

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0xba73…4b9d
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0x0403…1b2e
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0x01cc…de1f
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0xb357…3f88
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0xee83…52ac
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0x294f…66b1
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0xdb47…ca35
4d ago in 0xa3faf4a6…666d $0.01 not in registry 0x65ed…f2d8
4d ago in 0xa3faf4a6…666d $0.00500 not in registry 0x3c4a…1e29
4d ago in 0xa3faf4a6…666d $0.00100 not in registry 0x7d79…56f2
5d ago in 0x515d935b…5f62 $0.05 not in registry 0xe3c9…ff7e
5d ago out 0x79ebde4b…7d53 $0.01 not in registry 0x7fdc…daaa
5d ago out 0xab62452b…a7bf $0.01 not in registry 0x43b9…d1fe
6d ago out 0xb075aa82…59d8 $0.06 not in registry 0x171f…7f23
6d ago out 0xb075aa82…59d8 $0.02 not in registry 0x7767…cbd5
6d ago out 0xb075aa82…59d8 $0.06 not in registry 0x8333…1e06
6d ago out 0xb075aa82…59d8 $0.02 not in registry 0xa16e…862f

Reference

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