risk data for machine payments
Endpoint
api.m2msentinel.com/v1/security/score/:address
How completely could this Base contract be checked, and on what grade of evidence. Separates checked-and-clean from could-not-be-checked, which automated callers otherwise conflate. Explicitly not a safety score.
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 4h ago | 400 | 114 ms | — | — | — | E_NO_402:400 |
| 4d ago | 400 | 138 ms | — | — | — | E_NO_402:400 |
| 4d ago | 400 | 141 ms | — | — | — | E_NO_402:400 |
Settlements to this wallet
| When | Payer | Amount | Facilitator | Transaction |
|---|---|---|---|---|
| 4d ago | 0x556d…0484 | $0.00500 | not in registry | 0x6b14f7…d6e2 |
Reference
| URL | https://api.m2msentinel.com/v1/security/score/:address |
| Sources | bazaar |
| Recipient per catalogue | 0x6d6c398390cfb88f1cd42715b84906a0bd6652aa |
| Price per catalogue | 0.020000 |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.