openwebninja-x402.vercel.app/api/play-store-apps/top-grossing-apps
1.Catalog declaration
| Resource URL | https://openwebninja-x402.vercel.app/api/play-store-apps/top-grossing-apps |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc0ccf68a8e61a4d25eecfcacd486e673e900de0a |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-14 21:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 261 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 238 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 485 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 137 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 329 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 2012 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 235 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 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 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 “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-05 19:022026-09-05 19:02 UTC | settled (nonce-bound) | 200 | 0x64c76fad…90b6 | 9029 ms |
| 10000 units (≈ $0.01 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/96cdb53b-7165-48ab-933a-d3e43715088d)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-03 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-29 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-28 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-21 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-20 | 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
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.