risk data for machine payments
Wallet
?
0x4bc62fc6ddb6ff708097cad3f85e4d10c138e23e
Base · role: payer · 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?
Payments sent
1
1 recipients
Spent
$1.3
First seen
5d ago
A score needs more than a single payment to mean anything.
Pays to
| Recipient | Payments | Amount |
|---|---|---|
| 0xff98d0a1…30d9 | 1 | $1.3 |
Recent activity
| When | Direction | Counterparty | Amount | Facilitator | Transaction |
|---|---|---|---|---|---|
| 5d ago | out | 0xff98d0a1…30d9 | $1.3 | not in registry | 0x79f1…5e8a |
Reference
| Address | 0x4bc62fc6ddb6ff708097cad3f85e4d10c138e23e |
| 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.