api.x402node.dev/domain/email-security
1.Catalog declaration
| Resource URL | https://api.x402node.dev/domain/email-security |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x4466d4a84b7c49a6a094ec6eef4a0712d6dd125e |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-12 13:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-06 16:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 441 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 292 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 2148 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 1696 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 2132 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 111 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 110 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 89 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 80 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-06 12:102026-09-06 12:10 UTC | settle_failed | 500 | — | 369 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-01 | delisted | {"status":"active"} | {"status":"delisted"} |
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.