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

api.particle.pro/v1/podcasts/entities/charts

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://api.particle.pro/v1/podcasts/entities/charts
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x59f3a6dcb6f482c53872dd8f8f9e1f9161a1c5f7
Declared price (base units)10000
Catalog statusdelisted (since 2026-10-06 21:38 UTC)
First seen / last seen2026-09-07 01:03 UTC / 2026-10-06 01:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-072026-10-05
Figure 1. Probe timeline, last 9 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-10-05 10:30 UTCGETfail402186 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913.
2026-09-29 10:30 UTCGETfail402303 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913.
2026-09-29 07:38 UTCGETfail4021084 msprice_mismatchDeclared 10000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913.
2026-09-25 10:30 UTCGETfail402104 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 11:24 UTCGETfail40277 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 12:35 UTCGETfail40298 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-14 11:24 UTCGETfail402104 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-10 11:24 UTCGETfail40274 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-07 11:24 UTCGETpass402102 ms—

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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