risk data for machine payments
Wallet
F
0xf7038b2a1741f50a5748845ed0f7b23dfe49e8db
Base · role: payer · score 26/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?
Payments sent
2
2 recipients
Spent
$0.00000
First seen
4d ago
Score
F
26 of 100
recomputed 2m 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 |
|---|---|---|
| 0x3fc3bfe0…ffb0 | 1 | $0.00000 |
| 0x59dc4e72…c9dd | 1 | $0.00000 |
Recent activity
| When | Direction | Counterparty | Amount | Facilitator | Transaction |
|---|---|---|---|---|---|
| 3d ago | out | 0x3fc3bfe0…ffb0 | $0.00000 | not in registry | 0x573a…8ecf |
| 4d ago | out | 0x59dc4e72…c9dd | $0.00000 | not in registry | 0xae51…dc58 |
Reference
| Address | 0xf7038b2a1741f50a5748845ed0f7b23dfe49e8db |
| 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.