risk data for machine payments
Wallet
D
0xfa333170950c628c0912af258a33f1fc71fbf5ad
Base · role: pays and receives · score 35/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_RECEIVES
Payments sent
3
2 recipients
Spent
$0.33
Payments received
5
1 payers
Received
$0.23
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
35 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
| Recipient | Payments | Amount |
|---|---|---|
| 0xbd32a945…e137 | 2 | $0.23 |
| 0x1370a29c…331d | 1 | $0.1 |
Recent activity
| When | Direction | Counterparty | Amount | Facilitator | Transaction |
|---|---|---|---|---|---|
| 47d ago | out | 0xbd32a945…e137 | $0.13 | not in registry | 0x72e8…51b7 |
| 47d ago | in | 0xe88d1359…9221 | $0.1 | not in registry | 0x5e24…a307 |
| 48d ago | in | 0xe88d1359…9221 | $0.01 | not in registry | 0x5503…e7ab |
| 48d ago | in | 0xe88d1359…9221 | $0.01 | not in registry | 0x026c…2997 |
| 49d ago | in | 0xe88d1359…9221 | $0.01 | not in registry | 0x4c5d…4bbb |
| 50d ago | out | 0xbd32a945…e137 | $0.1 | not in registry | 0xee03…55c8 |
| 50d ago | in | 0xe88d1359…9221 | $0.1 | not in registry | 0x8125…4cb2 |
| 50d ago | out | 0x1370a29c…331d | $0.1 | not in registry | 0xe03f…61cf |
Reference
| Address | 0xfa333170950c628c0912af258a33f1fc71fbf5ad |
| Network | Base eip155:8453 |
| Sanctions screening | clear |
| 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.