risk data for machine payments
Wallet
F
0xc93a5f3abe1794d880c6dbad2606ea0d7688e1d3
Base · role: payer · score 21/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.01
First seen
5d ago
Score
F
21 of 100
recomputed 14h 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 |
|---|---|---|
| 0x6e007731…b04c | 1 | $0.00850 |
| 0xe9030014…1abf | 1 | $0.00200 |
Recent activity
| When | Direction | Counterparty | Amount | Facilitator | Transaction |
|---|---|---|---|---|---|
| 3d ago | out | 0x6e007731…b04c | $0.00850 | not in registry | 0x48a1…f1f0 |
| 5d ago | out | 0xe9030014…1abf | $0.00200 | not in registry | 0x370d…fd3f |
Reference
| Address | 0xc93a5f3abe1794d880c6dbad2606ea0d7688e1d3 |
| 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.