Wallet

D

0xe14bca2ab4939361b9e054dabd17ad1474d7adaf

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
52%
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
13
1 recipients
Spent
$0.04
Payments received
5
2 payers
Received
$0.08
First seen
50d 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
0xb2ac0c6c…0678 13$0.04

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
44d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0xad2c…f7c6
44d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x806c…ca7a
45d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x51d7…133d
45d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0xca53…fa48
46d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x79fe…3ee1
46d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x12dd…3a1c
46d ago in 0x0241e370…692b $0.01 PayAI 0xe1aa…0f83
46d ago in 0x0241e370…692b $0.01 PayAI 0x82cc…3a04
46d ago in 0x0241e370…692b $0.03 PayAI 0x6772…923a
46d ago in 0x0241e370…692b $0.02 PayAI 0xde44…7c09
47d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0xad98…5612
48d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x8583…4593
48d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x9aba…ca4b
49d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0xf098…e7e7
49d ago in 0x4735a687…be1b $0.00500 PayAI 0x96de…55cb
49d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0xc507…10ba
50d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0xccf1…5958
50d ago out 0xb2ac0c6c…0678 $0.00300 not in registry 0x141b…719a

Reference

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