api.particle.pro/v1/podcasts/rankings
1.Catalog declaration
| Resource URL | https://api.particle.pro/v1/podcasts/rankings |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x59f3a6dcb6f482c53872dd8f8f9e1f9161a1c5f7 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-09-07 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 919 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 273 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 414 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 327 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 211 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 1942 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 359 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 266 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 307 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 2363 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 374 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 434 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 406 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 mismatch- the response lacked fields the listing's output schema declares.
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).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-09 07:012026-09-09 07:01 UTC | settled (nonce-bound) | 200 | 0xed0f88ff…fc25 | 1560 ms |
| 30000 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 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/62d77433-0888-427e-a078-a11837801d16)4.Catalog listing events
No listing changes observed.
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.
About the purchase at 2026-09-09T07:01:00Z (UTC). The form starts with that time; add what you saw instead.