Wallet

F

0x3cedc3cba49c3809ee46b9bf60da75d6607b45ec

Base · role: pays and receives · score 19/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
7
1 recipients
Spent
$0.00900
Payments received
8
1 payers
Received
$0.00900
First seen
3d 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
19 of 100
recomputed 6m 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
0xb3f32bdf…a69d 7$0.00900

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
3d ago out 0xb3f32bdf…a69d $0.00200 not in registry 0x57b4…405d
3d ago in 0xb3f32bdf…a69d $0.00200 not in registry 0xe146…4a40
3d ago out 0xb3f32bdf…a69d $0.00200 not in registry 0x3273…347e
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0xf830…2fc1
3d ago out 0xb3f32bdf…a69d $0.00100 not in registry 0x0d88…4b05
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0x77f9…dc35
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0x2f1e…1fcf
3d ago out 0xb3f32bdf…a69d $0.00100 not in registry 0xc39e…cc07
3d ago out 0xb3f32bdf…a69d $0.00100 not in registry 0x101d…bf79
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0xb979…0aaf
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0xe0e8…2e64
3d ago out 0xb3f32bdf…a69d $0.00100 not in registry 0x9824…a964
3d ago out 0xb3f32bdf…a69d $0.00100 not in registry 0xe6ec…02ce
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0xa3f6…e637
3d ago in 0xb3f32bdf…a69d $0.00100 not in registry 0xf6fb…9f58

Reference

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