Wallet

D

0xd87812d1c8c547fb4793dbcc801fc769589ba8db

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_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
14
1 recipients
Spent
$0.23
Payments received
1
1 payers
Received
$0.05
First seen
46d 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 14d 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
0xbba594f5…5f86 14$0.23

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
45d ago out 0xbba594f5…5f86 $0.01 not in registry 0x1f09…9a67
45d ago in 0xbba594f5…5f86 $0.05 not in registry 0xa42c…ce72
45d ago out 0xbba594f5…5f86 $0.08 not in registry 0xa790…0ef3
46d ago out 0xbba594f5…5f86 $0.00900 not in registry 0x0d29…a1b6
46d ago out 0xbba594f5…5f86 $0.00400 not in registry 0x17b6…74bb
46d ago out 0xbba594f5…5f86 $0.00900 not in registry 0x9bed…d7f8
46d ago out 0xbba594f5…5f86 $0.02 not in registry 0xea71…49ad
46d ago out 0xbba594f5…5f86 $0.02 not in registry 0x64f8…3898
46d ago out 0xbba594f5…5f86 $0.01 not in registry 0xa1a7…9bf5
46d ago out 0xbba594f5…5f86 $0.01 not in registry 0x1de8…5b77
46d ago out 0xbba594f5…5f86 $0.00400 not in registry 0xe12d…9864
46d ago out 0xbba594f5…5f86 $0.02 not in registry 0x4f48…b7c8
46d ago out 0xbba594f5…5f86 $0.01 not in registry 0x9375…dbef
46d ago out 0xbba594f5…5f86 $0.02 not in registry 0x3c33…c1d9
46d ago out 0xbba594f5…5f86 $0.00400 not in registry 0xb794…3226

Reference

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