Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-13 · 19 days ago
vet402Back to the registerMethodology

api.x402dataapi.com/v1/mail-security

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.x402dataapi.com/v1/mail-security
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xe3e597a4698e0ed0e06f9d9fe513157728fbc28b
Declared price (base units)1000
Catalog statusdelisted (since 2026-09-14 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-13 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-142026-09-13
Figure 1. Probe timeline, last 25 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-13 22:40 UTCPOSTfail402470 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-13 13:40 UTCPOSTfail402408 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-12 16:40 UTCPOSTfail402496 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-12 04:40 UTCPOSTfail402555 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-11 16:40 UTCPOSTfail402483 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-10 23:40 UTCPOSTfail402583 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-10 14:40 UTCPOSTfail402501 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-09 23:40 UTCPOSTfail402514 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-09 05:40 UTCPOSTfail402558 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-08 17:40 UTCPOSTfail402559 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-08 05:40 UTCPOSTfail402569 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-07 17:40 UTCPOSTfail402458 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-07 05:40 UTCPOSTfail402588 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-06 17:40 UTCPOSTfail402664 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-05 23:40 UTCPOSTfail402445 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-05 14:40 UTCPOSTfail402556 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-04 23:40 UTCPOSTfail402492 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-04 14:40 UTCPOSTfail402389 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-03 23:40 UTCPOSTfail402546 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-03 14:40 UTCPOSTfail402584 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-03 05:40 UTCPOSTfail402472 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-02 14:40 UTCPOSTfail402508 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-02 05:40 UTCPOSTfail402634 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-01 23:40 UTCPOSTfail402932 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-08-14 08:52 UTCPOSTpass402719 ms—

3.L1 — real purchases

1 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.

1 of those paid attempts are held as inconclusive rather than counted against this seller (1 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).

Terms in this table

settled (amount + payee)
vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
settled_4xx
held_reason in the export: the payment settled, then the paid request got a 4xx.
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).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
08-14 10:05settled (amount + payee)4000x73c830b7…c4c71516 ms
1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 delivered · 1 inconclusive 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 0 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. 1 paid attempt is held as inconclusive rather than counted against the seller: a paid request that answered 4xx, settled or not, can be our own request being malformed, because vet402 buys with no API key and sends a request body only when the seller declares one; and a 402 or 5xx from 2026-09-13 to 2026-09-15 came while vet402's own payer wallet was out of USDC. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (api.x402dataapi.com · measured 2026-08-14)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/028a5cc5-223a-4cc7-8174-fbaad7c305e6.svg)](https://vet402.com/observatory/e/028a5cc5-223a-4cc7-8174-fbaad7c305e6)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-14delisted{"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.

20–2,000 characters · 0 so far