Wallet

?

0x550e58c2430890b199afb56f4865e4ff7b897ada

Base · role: pays and receives · not enough data

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
Payments sent
1
1 recipients
Spent
$1
Payments received
3
1 payers
Received
$31.4
First seen
4d 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.
A score needs more than a single payment to mean anything.

Pays to

RecipientPaymentsAmount
0xa97eea7d…42e7 1$1

Recent activity

WhenDirectionCounterpartyAmountFacilitatorTransaction
3d ago in 0x13de1e11…883e $5 not in registry 0x2e56…e720
3d ago in 0x13de1e11…883e $20 not in registry 0x3344…09fc
3d ago in 0x13de1e11…883e $6.4 not in registry 0xe35e…7d0a
4d ago out 0xa97eea7d…42e7 $1 not in registry 0x36e9…b244

Reference

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