risk data for machine payments
Wallet
0x3a36fd8818074255620dae7cf3bce9649a689f32
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?
Measured from how evenly the payments are spaced: a machine keeps the same interval, a human does not. Here the intervals are almost perfectly regular — this is automation.
Regular intervals mean automation, not necessarily an AI agent: a cron script looks exactly the same. TRM Labs put the share of value from autonomous agents at somewhere between 0.6% and 7.5%; the rest is ordinary scripts.
That is why agent likelihood is reported separately rather than folded into the score.
Score
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 |
|---|---|---|
| 0x5aae638c…482e | 4 | $1 |
Recent activity
| When | Direction | Counterparty | Amount | Facilitator | Transaction |
|---|---|---|---|---|---|
| 3d ago | out | 0x5aae638c…482e | $0.25 | not in registry | 0x9b31…d099 |
| 5d ago | out | 0x5aae638c…482e | $0.25 | not in registry | 0x4595…b8fd |
| 6d ago | out | 0x5aae638c…482e | $0.25 | not in registry | 0xf2ae…78fe |
| 6d ago | out | 0x5aae638c…482e | $0.25 | not in registry | 0xe678…f714 |
Reference
| Address | 0x3a36fd8818074255620dae7cf3bce9649a689f32 |
| 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.