Wallet

D

0xeb729fb299b48a9e8af71608dd068b1a3c867d6a

Base · role: pays and receives · score 33/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
12
1 recipients
Spent
$0.08
Payments received
1
1 payers
Received
$0.2
First seen
49d 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
33 of 100
recomputed 13d 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
0x9acfdc5a…2abf 12$0.08

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
45d ago out 0x9acfdc5a…2abf $0.00100 not in registry 0xdd48…0c9d
45d ago out 0x9acfdc5a…2abf $0.00200 not in registry 0x0e46…1776
45d ago out 0x9acfdc5a…2abf $0.00100 not in registry 0x36b9…9e16
47d ago out 0x9acfdc5a…2abf $0.01 not in registry 0x9357…9f38
47d ago in 0x9c5801aa…a217 $0.2 not in registry 0x1003…5b6d
48d ago out 0x9acfdc5a…2abf $0.00100 not in registry 0x830c…b699
48d ago out 0x9acfdc5a…2abf $0.00100 not in registry 0x660a…380f
49d ago out 0x9acfdc5a…2abf $0.01 not in registry 0x74da…ceb0
49d ago out 0x9acfdc5a…2abf $0.01 not in registry 0xf8c5…4b90
49d ago out 0x9acfdc5a…2abf $0.01 not in registry 0x7bbc…99d7
49d ago out 0x9acfdc5a…2abf $0.01 not in registry 0x3bde…c34b
49d ago out 0x9acfdc5a…2abf $0.01 not in registry 0xb79f…2648
49d ago out 0x9acfdc5a…2abf $0.01 not in registry 0x5712…1941

Reference

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