google-trends.use.x402atlas.com/interest-by-region
1.Catalog declaration
| Resource URL | https://google-trends.use.x402atlas.com/interest-by-region |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x9aaceabad8e1858b72fcea1665381b168841b2fa |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 56 / 8 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 48 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 397 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 591 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 5 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 2041 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 2006 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 5 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 51 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 205 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 386 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 17 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 2097 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 23 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 46 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 157 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 match- the response had the 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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-11 01:022026-09-11 01:02 UTC | settled (nonce-bound) | 200 | 0x027986a6…dbd3 | 923 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-28 12:202026-08-28 12:20 UTC | settled (amount + payee) | 200 | 0xfe86f954…53a4 | 2333 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-21 12:202026-08-21 12:20 UTC | settled (amount + payee) | 200 | 0x306cd375…09ba | 2679 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-14 10:042026-08-14 10:04 UTC | settled (amount + payee) | 200 | 0xeb4712a2…ab6a | 2840 ms |
| 30000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/cc5c9ed5-ca6b-41f5-a730-a855ed967435)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.