pennyrail.vercel.app/api/bazaar/hacker-news
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
| Resource URL | https://pennyrail.vercel.app/api/bazaar/hacker-news |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x0b53378117e82b50afba71d794a21c22c7e36d2c |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-09-12 01:03 UTC) |
| First seen / last seen | 2026-09-01 01:03 UTC / 2026-09-11 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-11 13:40 UTC | POST | fail | 503 | 107 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-09-10 23:40 UTC | POST | fail | 503 | 1940 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 354 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 443 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 102 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 195 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 460 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-06 14:40 UTC | POST | pass | 402 | 277 ms | — |
| 2026-09-05 23:40 UTC | POST | pass | 402 | 564 ms | — |
| 2026-09-05 14:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-09-04 23:40 UTC | POST | pass | 402 | 49 ms | — |
| 2026-09-04 14:40 UTC | POST | pass | 402 | 192 ms | — |
| 2026-09-03 23:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-09-03 14:40 UTC | POST | pass | 402 | 81 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 439 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).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-08 07:012026-09-08 07:01 UTC | settled (nonce-bound) | 200 | 0x093b3e4d…d991 | Base | 1192 ms |
| 5000 units (≈ $0.005 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.
[](https://vet402.com/observatory/e/343b2c14-eec9-4ebc-b64a-3d8f66d3fa44)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-12 | 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
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.