risk data for machine payments
Endpoint
api.agentmercantile.com/v1/payment-authority-snapshot
Produce a factual snapshot of current x402 payment authority for one unpaid v2 requirement and one public EVM payer: selected scheme/network/asset/amount/payTo/transfer method, same-block token balance, canonical token-spender allowance when that path applies, and declared recovery-path classification. Does not sign, approve, construct a transaction, judge native gas, or recommend whether to buy.
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 | 82 ms | — | — | — | E_NO_402:404 |
| 21d ago | 404 | 81 ms | — | — | — | E_NO_402:404 |
| 44d ago | 404 | 92 ms | — | — | — | E_NO_402:404 |
| 45d ago | 404 | 119 ms | — | — | — | E_NO_402:404 |
| 49d ago | 404 | 126 ms | — | — | — | E_NO_402:404 |
| 49d ago | 404 | 123 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/payment-authority-snapshot |
| Sources | well-known bazaar |
| Recipient per catalogue | 0xdb7b2b54f80479826222749a2ea73a8acc306e1e |
| Price per catalogue | 0.005000 |
| 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.