risk data for machine payments
Endpoint
api.agentmercantile.com/v1/x402-service-change-snapshot
Determine whether a previously accepted x402 service payment contract is still equivalent enough to proceed. Compares one live unpaid 402 challenge, using a caller-supplied GET or POST request shape, against a caller-held baseline bound to that request identity. Not uptime monitoring, a trust score, a webhook, a marketplace crawl, or a generic POST {} probe of every x402 resource.
prepay verdict
in that case is warn: unknown is a risk, not a clean bill of health.Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 20d ago | 404 | 80 ms | — | — | — | E_NO_402:404 |
| 21d ago | 404 | 81 ms | — | — | — | E_NO_402:404 |
| 44d ago | 404 | 89 ms | — | — | — | E_NO_402:404 |
| 45d ago | 404 | 119 ms | — | — | — | E_NO_402:404 |
| 49d ago | 404 | 285 ms | — | — | — | E_NO_402:404 |
| 49d ago | 404 | 127 ms | — | — | — | E_NO_402:404 |
Settlements to this wallet
| When | Payer | Amount | Facilitator | Transaction |
|---|---|---|---|---|
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0x249bec…f2b1 |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0x7b6d07…c690 |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0x10271f…178c |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0xe5dcd1…9b34 |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0x84d5b8…c5c0 |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0x8319cb…89df |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0xf4cd0b…1b06 |
| 46d ago | 0xec2a…d034 | $0.01 | not in registry | 0xf55bfd…2c98 |
Reference
| URL | https://api.agentmercantile.com/v1/x402-service-change-snapshot |
| Sources | well-known bazaar |
| Recipient per catalogue | 0xdb7b2b54f80479826222749a2ea73a8acc306e1e |
| Price per catalogue | 0.010000 |
| 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.