ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/website_due_diligence
1.Catalog declaration
| Resource URL | https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/website_due_diligence |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8647f7d7a1368a467ad1ff757fbc2e7167973558 |
| Declared price (base units) | 40000 |
| Catalog status | active |
| First seen / last seen | 2026-08-15 01:36 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 04:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 350 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 183 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 191 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 112 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 1940 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 221 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 151 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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.
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-17 18:012026-09-17 18:01 UTC | settled (nonce-bound) | 200 | 0x8f4bafdc…3412 | 3178 ms |
| 40000 units (≈ $0.04 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 19:022026-09-10 19:02 UTC | settled (nonce-bound) | 200 | 0x7b1b7099…c4b9 | 3804 ms |
| 40000 units (≈ $0.04 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 01:002026-09-02 01:00 UTC | settled (amount + payee) | 200 | 0x570e1f9f…2154 | 2099 ms |
| 40000 units (≈ $0.04 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/a957ebba-c3ea-48a4-beaf-1dc87f54ea8a)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.