risk data for machine payments
Endpoint
api.invoket.com/preflight/x402-seller
Before your agent signs an x402 payment to a counterparty it does not know: submit the 402 challenge you received and get one verdict - ok, review, stop, insufficient_coverage - over the pay-to address screened against the OFAC, EU and UN designation lists, the amount claimed compared with what that resource publishes in the public CDP Bazaar census, and whether the resource is listed at all. Every reason names its block and its source.
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 |
|---|---|---|---|---|---|---|
| 1h ago | 402 | 36 ms | exact eip155:8453 |
0x4465…28ee | 0.250000 | clean |
| 7h ago | 402 | 161 ms | exact eip155:8453 |
0x4465…28ee | 0.250000 | clean |
| 4d ago | 402 | 415 ms | exact eip155:8453 |
0x4465…28ee | 0.250000 | clean |
| 4d ago | 402 | 412 ms | exact eip155:8453 |
0x4465…28ee | 0.250000 | clean |
Reference
| URL | https://api.invoket.com/preflight/x402-seller |
| Sources | well-known |
| Recipient per catalogue | 0x4465825B0ac713aA2Fa07Ea29023020804A128ee |
| 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.