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

whaletape.xyz/recommendations

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://whaletape.xyz/recommendations
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x25a8b697da5c0baf698fd6bd9701b5e825214145
Declared price (base units)10000
Catalog statusdelisted (since 2026-10-01 01:03 UTC)
First seen / last seen2026-08-23 01:18 UTC / 2026-09-30 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-102026-09-30
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-30 22:40 UTCGETfail402581 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-29 22:40 UTCGETfail402743 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-29 10:30 UTCGETfail402955 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 50000 of EPjFWd…Dt1v, 50000 of 0x8335…2913, 50000 of 0xaf88…5831, 50000 of 0x5fc5…d168.
2026-09-29 04:40 UTCGETfail4022432 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-28 13:40 UTCGETfail4022474 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 16:40 UTCGETfail4022345 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 22:40 UTCGETpass402455 ms—
2026-09-26 04:40 UTCGETpass402501 ms—
2026-09-25 13:40 UTCGETpass402467 ms—
2026-09-24 16:40 UTCGETpass4022248 ms—
2026-09-23 22:40 UTCGETpass402401 ms—
2026-09-23 04:40 UTCGETpass402396 ms—
2026-09-22 13:40 UTCGETpass402411 ms—
2026-09-21 16:40 UTCGETpass402467 ms—
2026-09-21 04:40 UTCGETpass402440 ms—
2026-09-20 13:40 UTCGETpass402466 ms—
2026-09-19 16:40 UTCGETpass402503 ms—
2026-09-18 22:40 UTCGETpass402433 ms—
2026-09-18 04:40 UTCGETpass402638 ms—
2026-09-17 13:40 UTCGETpass402683 ms—
2026-09-16 22:40 UTCGETpass402492 ms—
2026-09-15 22:40 UTCGETpass402657 ms—
2026-09-15 13:40 UTCGETpass402821 ms—
2026-09-14 16:40 UTCGETpass402450 ms—
2026-09-13 22:40 UTCGETpass402433 ms—
2026-09-13 13:40 UTCGETpass402651 ms—
2026-09-12 22:40 UTCGETpass402657 ms—
2026-09-12 04:40 UTCGETpass402799 ms—
2026-09-11 16:40 UTCGETpass402522 ms—
2026-09-10 23:40 UTCGETpass402675 ms—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 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 (nonce-bound)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and 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.
L2 no_declaration
the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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).
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 txPayment chainLatency
09-09 19:01settled (nonce-bound)2000x12b04df1…104eBase1951 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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: 1 of 1 paid attempts settled with an on-chain receipt, and 1 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. (whaletape.xyz · measured 2026-09-09)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/cc728eae-e22e-4a50-9138-61c072d5551e.svg)](https://vet402.com/observatory/e/cc728eae-e22e-4a50-9138-61c072d5551e)

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-10-01delisted{"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