email-verify-api-production-d262.up.railway.app/verify
1.Catalog declaration
| Resource URL | https://email-verify-api-production-d262.up.railway.app/verify |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xffc458db291b4abce020fe3de4f91f2770e537b1 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | POST | pass | 402 | 179 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 117 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 114 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 137 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 275 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 308 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 297 ms | — |
| 2026-10-07 22:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 282 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 208 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 1952 ms | — |
| 2026-10-03 22:40 UTC | POST | pass | 402 | 244 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 335 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 326 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 277 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 394 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 427 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 304 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 117 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 324 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 386 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 111 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 120 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 119 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 240 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 match- the response had the fields the listing's output schema declares.
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 |
|---|---|---|---|---|
| 10-08 18:012026-10-08 18:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x6f4db66a…0d88 | 1637 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-29 18:022026-09-29 18:02 UTC | settled (nonce-bound)tx from our index | 200 | 0x64afed14…993f | 1513 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-22 00:002026-09-22 00:00 UTC | settled (nonce-bound)tx from our index | 200 | 0xd91d841d…4375 | 1236 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/42328326-d553-4d7f-aea6-90849057b177)4.Catalog listing events
No listing changes observed.
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.