Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-09-20 · 34 days ago
vet402Back to the registerMethodology

oracle.the-undesirables.com/api/v1/trending

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://oracle.the-undesirables.com/api/v1/trending
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x642e8a7c289381f24f0395e0539f0ba41c74cc1b
Declared price (base units)25000
Catalog statusdelisted (since 2026-09-21 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-20 01:03 UTC
Catalog-reported calls / payers (30d)4 / 3

2.Probe history

2026-09-032026-09-20
Figure 1. Probe timeline, last 30 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-20 22:40 UTCGETfail200415 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-20 04:40 UTCGETfail530486 msno_402HTTP 530 instead of 402 to an unpaid GET.
2026-09-19 13:40 UTCGETfail200261 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-18 16:40 UTCGETfail200107 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-18 04:40 UTCGETfail200377 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-17 13:40 UTCGETfail200228 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-16 16:40 UTCGETfail200320 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-15 22:40 UTCGETfail200169 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-15 04:40 UTCGETfail200216 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-14 13:40 UTCGETfail200186 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-13 22:40 UTCGETfail200192 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-13 04:40 UTCGETfail200295 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-12 16:40 UTCGETpass40266 ms—
2026-09-12 04:40 UTCGETpass402273 ms—
2026-09-11 13:40 UTCGETpass402271 ms—
2026-09-10 23:40 UTCGETpass402181 ms—
2026-09-10 14:40 UTCGETpass402396 ms—
2026-09-09 17:40 UTCGETpass402256 ms—
2026-09-09 05:40 UTCGETpass4022056 ms—
2026-09-08 17:40 UTCGETpass402198 ms—
2026-09-08 05:40 UTCGETpass402184 ms—
2026-09-07 17:40 UTCGETpass402134 ms—
2026-09-06 23:40 UTCGETpass4021645 ms—
2026-09-06 14:40 UTCGETpass4022143 ms—
2026-09-05 23:40 UTCGETpass402240 ms—
2026-09-05 14:40 UTCGETpass402177 ms—
2026-09-04 23:40 UTCGETpass402177 ms—
2026-09-04 14:40 UTCGETpass402223 ms—
2026-09-03 23:40 UTCGETpass402179 ms—
2026-09-03 14:40 UTCGETpass402385 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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

settled (amount + payee)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 mismatch
the content type was not JSON although the listing marks required keys, or the body read in full did not parse as JSON, was JSON but not an object or array, or lacked a key the listing marks as required.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
3/3
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 txPayment chainLatency
08-31 12:08settled (amount + payee)2000xc0b83960…8841Base9478 ms
25000 units (≈ $0.03 USDC) · L2 mismatchWhose side: no failure (delivered)
08-21 12:22settled (amount + payee)2000x5f808d5e…5297Base8361 ms
25000 units (≈ $0.03 USDC) · L2 mismatchWhose side: no failure (delivered)
08-14 10:05settled (amount + payee)2000xddd574e3…f171Base7578 ms
25000 units (≈ $0.03 USDC) · L2 mismatchWhose 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.

vet402: 3 of 3 paid attempts settled with an on-chain receipt, and 3 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (oracle.the-undesirables.com · measured 2026-08-31)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/aae5d109-cdbe-495e-aedf-f900d2303353.svg)](https://vet402.com/observatory/e/aae5d109-cdbe-495e-aedf-f900d2303353)

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-21delisted{"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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far